.svg?fit=max&auto=format&n=mBaWmVpTOpDBIB6_&q=85&s=36c7989ebe591de9ac7d3618f0a04a28)
.svg?fit=max&auto=format&n=mBaWmVpTOpDBIB6_&q=85&s=5afe473ba3ef2469d3e839045bcb099c)
Owner
The single owner is the person who created the organization. They have full access to everything: all Meridian features, all apps in the organization, all settings including billing and team management. Meridian automatically assigns the owner role to the person who creates the account. There is exactly one owner per organization. The owner exists above the role system and cannot be restricted by anyone else. Three things belong to the owner alone and can’t be granted through a role: transferring ownership, deleting the organization, and staying put. The owner can’t be removed and can’t leave without first handing ownership over. Ownership is transferred through organization settings, and only the current owner can initiate that transfer.Team members
A team member is anyone invited by email into the organization by someone with the Team members: Edit permission (the owner and admins have it by default). Every team member has a role assigned at invitation. That role defines what they can see and do across the organization and its apps. Team member access can be changed or removed at any time by anyone with Team members: Edit. A team member who isn’t the owner can leave the organization at any time without any permission.Roles
A role is a named configuration that defines what a team member can see and do. Roles have two categories of permissions:
Roles can be default roles provided by Meridian or custom roles created by anyone with the Roles: Edit permission. A single role can be assigned to multiple team members.
For the default roles Meridian provides, see Roles.
Inviting a team member
The owner, admins, and any team member whose role holds Team members: Edit can invite new team members, change roles, and remove access. Invitations are sent by email from Organization settings under Team. The invitee receives an email with a link to register or sign in and confirm the invitation. Every invitation requires a role to be selected before it’s sent. The role takes effect the moment the invitee accepts, and it is the only role they hold: a role limited to some apps gives them those apps and nothing else. If the invitee doesn’t have a Meridian account, they create one as part of accepting the invitation. If they already have an account under that email address, they’re added to the organization on sign-in.Changing a team member’s role
Roles can be changed at any time from Organization settings under Team. The change takes effect immediately. The team member doesn’t need to sign out and back in. Changing a role needs Team members: Edit. A non-owner can only re-role a member whose permissions they hold themselves, and cannot assign a role with more permissions than their own.Removing a team member
Removing a team member revokes their access to the organization immediately. They lose access to all apps and settings in that organization. Their account is not deleted; they no longer belong to this organization. If the removed team member belongs to other organizations in Meridian, their access to those is unaffected. What the removed team member sees next depends on what they still belong to:- The organization was the one they had open, and they belong to another one. Meridian switches them to one of their remaining organizations (their own organization first, if they have one) and opens its usual landing page. A page they still have open moves on its own the next time it reaches the removed organization, and refreshing or signing in again lands them there too.
- It was their only organization. This is typically someone who joined through an invitation and never created an organization of their own. Their account stays, and they are taken to the first onboarding step with a notice: “You were removed from your organization. You no longer belong to any organization. Create your own organization to continue.” Nothing is created or billed until they finish onboarding themselves.
- It was not the organization they had open. They stay in the organization they are working in.