Organizations in Zenifra
Organizations are the main context for using resources in Zenifra. Each CPF or CNPJ account receives an organization at sign-up, and the same user account can participate in multiple organizations by accepting invitations.
This model lets you separate personal projects, companies, clients, and teams without creating multiple user accounts. When you switch the active organization in the console, you change the set of projects, databases, AI keys, API Keys, Git connections, billing data, and members available in that context.
How it works
An organization represents the workspace where resources are created and managed. HTTP projects, managed databases, AI keys, deploy integrations, and billing data belong to the active organization.
| Concept | Description |
|---|---|
| Personal organization | Created at sign-up for an account with a CPF |
| Business organization | Created at sign-up for an account with a CNPJ |
| Active organization | Console context selected to create, view, and manage resources |
| Member | User invited to collaborate in an organization |
When you create a project, it is associated with the organization selected at that moment. To view or change that project later, you must be in the same organization and have enough permission.
Multiple organizations per user
A user can participate in several organizations with the same login. Each account has its own organization, created at sign-up; to join another one, the person must be invited by whoever manages that organization. This is useful for people who work in more than one company or serve different clients.
Common examples:
- a person has a personal organization and also participates in the company organization;
- a consulting company is invited to each client's organization;
- a finance owner participates only in the organization where cost tracking is needed.
Permissions are evaluated per organization. Broad access in one organization does not automatically grant access to another one.
Roles and responsibilities
Zenifra uses roles to define each member's base access level.
| Role | Recommended use |
|---|---|
| Owner | Main organization owner responsible for billing, members, and permissions |
| Assistant | Trusted person who operates projects, databases, managed services, and AI keys and helps invite members |
| Member | Collaborator who starts with no permissions and receives only the required access |
Each organization has a single owner, with full administrative access. assistant and member depend on granular permissions, granted directly or through reusable policies, for specific resources and actions, such as viewing project logs, changing environment variables, triggering deploys, or checking transactions.
Security and collaboration
Organizations help enforce least privilege. Instead of sharing one account, each person uses their own user and receives only the access they need.
Good practices:
- invite users by the correct Zenifra account email;
- prefer specific permissions for critical projects;
- review active members periodically;
- remove access when someone leaves the team;
- avoid granting billing or environment variable permissions unless required.
This workflow reduces operational risk, improves traceability, and makes collaboration easier for technical, financial, and administrative users.
Next steps
FAQ
Does every account have an organization?
Yes. CPF and CNPJ accounts receive an organization at sign-up and operate through it, even when only one person uses the account.
Can I participate in more than one organization?
Yes. The same user can accept invitations from other organizations and switch context in the console.
Are projects shared between organizations?
No. Projects belong to the organization where they were created. To access them, the user must be in that organization and have the right permission.
Last updated on