Organizations and projects
As a Logfire user, you can be part of multiple organizations, and each organization can have multiple projects.
There are two types of organizations:
- Personal organizations: this is the default organization created when you sign up. You are the owner of this organization, but can invite other people.
- Normal organizations: these can be created separately from the personal one.
Both organization types are functionally equivalent and you can invite others to all of them.
Multiple projects can be created in organizations, and they can be either public (within the organization) or private (see roles below). Depending on the user's organization role, they may have implicit access to the organization projects.
Which organization type should I use?¶
While you can use your personal org for production use-cases (e.g. if you are working alone or in a small team), you may wish to switch your personal org to a normal org if you are working at a larger company and want to create a more "official" Logfire org for that company. This also means you don't have to share your personal org's projects (which you may wish to keep private) with any colleagues.
See the step-by-step guide to converting your personal account to an organization for screenshots and detailed instructions.
Roles¶
Logfire provides a fixed set of organization and project roles, that can be managed in the organization settings. Roles contain a set of permissions, and are assigned to team members either at the organization or project level.
Organization roles¶
Every user in your organization has an organization role assigned. They contain organization permissions (e.g. create_project),
as well as project permissions (e.g. read_dashboard), which apply to projects the user have access to (unless they have an explicit
project role on some projects).
Three organization roles are available:
| Role | Description | Project access | Editable |
|---|---|---|---|
| Admin | Gives all permissions. This is the role assigned to you when creating an organization | Public and private projects | ❌ |
| Member | Has a specific set of organization and project permissions, which can be changed. | Public projects | ✅ |
| Guest | Assigned to users when they are invited directly to a project of the organization. | None | ❌ |
Project roles¶
When a user is part of an organization, they have access to the projects of that organization according to the project access policy described in the organization roles table.
However, users can also be invited directly to a project, in which case a project role is being assigned to them (and they are added to the organization as guests). Of course, it is possible to assign a specific project role to an existing organization user, in which case the project permissions from their organization role will not apply.
Three project roles are available:
| Role | Description | Editable |
|---|---|---|
| Admin | Gives all permissions. | ❌ |
| Write | Has a specific set of edit permissions, which can be changed. | ✅ |
| Read | Has only read permissions. | ❌ |
Custom roles and externally managed teams¶
Organizations using the entreprise plan have the ability to create custom roles (on top of the existing ones), as well as using external identity and access management providers such as Microsoft Entra ID.