Team collaboration

Eanvi scopes work to organizations. Invite teammates, assign roles, and rely on audit logs instead of shared password managers for .env files.

Invite a member

1. Open Settings → organization / members (or the organization members page).
2. Enter their email and choose a role.
3. Send the invite.
4. They accept via the invite link and join the org.

Pending invites appear until accepted or revoked.

Roles

Exact labels may vary by plan, but access generally follows:

Always verify permissions in your org before granting production reveal rights.

API keys for machines

Humans use session login (or CLI login). CI and services should use API keys:

1. Settings → API keys.
2. Create a key with a descriptive name (for example github-actions-prod).
3. Copy the token once (eanvi_sk_...).
4. Store it in the CI secret store — never in git.

Rotate or revoke keys when people leave or pipelines change.

Audit activity

Organization Audit Activity records sensitive events such as:

• Secret create / update / delete
• Reveal and export
• Member invite and role changes
• CLI push / sync operations (where instrumented)

Use audit logs during incident review and access reviews.

Working agreements that scale

1. One org per company or product line; projects per service.
2. Separate development / staging / production environments.
3. Prefer CLI pull in onboarding over Slack pastes.
4. Restrict production reveal to owners/admins.
5. Require API keys (not personal passwords) in CI.

Next steps

• Getting started
• CI/CD guide
• Security best practices