Teams and roles
Organizations, members and roles, two-factor authentication, API keys and the audit log.
Organizations
Everything in Lahyer belongs to an organization: projects, domains, databases, billing and the people who work on them. Signing up creates a personal organization for you; create more for teams and clients, and switch between them in the dashboard. Each organization has its own plan.
Invite people
On Settings, Members, use Invite someone with an email address and a role. Invitations are valid for 7 days. Members and pending invitations together count toward the plan's limit: 5 people on Free, 50 on Pro.
Roles
| Owner | Admin | Member | |
|---|---|---|---|
| Create projects, deploy, read logs and analytics | Yes | Yes | Yes |
| Change settings, environment variables, domains and cron jobs | Yes | Yes | Yes |
| Delete or move projects, remove databases | Yes | Yes | No |
| Payment keys and products, site accounts | Yes | Yes | No |
| Invite and manage members, create API keys | Yes | Yes | No |
| Billing, plan and Studio credits | Yes | No | No |
| Delete the organization | Yes | No | No |
Admins manage members and other admins but not owners; only an owner can make someone an owner. Nobody changes their own role.
Two-factor authentication
On Settings, Account, turn on Two-factor authentication: scan the code with an authenticator app and save the backup codes, which are shown once. Sign-ins with your password then ask for a code. The Devices card on the same page shows where you are signed in.
API keys
The CLI and your own scripts act with API keys, created by owners and admins on Settings, API keys:
- A key acts inside one organization, as an Admin or a Member.
- Keys expire after 30 days, 90 days or a year, or never.
- A key starts with
lhy_and is shown once, when you create it. - An organization can hold 20 keys.
- Keys cannot manage people, other keys or sessions.
Audit log
Settings, Audit log records who did what and when: deployments, setting changes, domain and environment variable edits (including each time a value is revealed), members, API keys and billing.
Move a project to another organization
On the project's Settings, Move to another organization hands it over to another organization you administer. Deployments, domains, environment variables and AI conversations move with the project; its addresses keep working and pushes keep deploying. You need the admin role in both organizations.