Organizations

How Axalot organizations, roles, invitations, join requests, active workspace selection, and access removal work.

What organizations do

An organization is the workspace boundary in Axalot. Console records are loaded inside the active organization, so the same user can see different data after switching organizations.

Workspace boundary

Tracker and META records are scoped to an organization.

Active context

One organization is current at a time for console work.

Member access

Only active memberships grant access to an active organization.

Module access

Enabled organization modules decide whether Tracker and META are available.

Users can belong to more than one organization. Axalot keeps one organization active for the console session and loads product data from that organization. Use this as a company/workspace switcher: moving from one organization to another changes the company context for the console.

State	What happens
User has one active organization	Axalot uses that organization for the console.
User has multiple active organizations	The selected organization is current until the user switches.
User leaves the current organization	Axalot selects another active organization when one exists, otherwise returns the user to Organizations.
Organization is inactive	It is not used for console access.

Account creation paths

There are two common ways to start using Axalot.

Path	Use when	Result
Create your own organization	You are setting up a company workspace or need your own Tracker/META environment.	Axalot creates the organization and makes you an `Active` `Admin`.
Join by invitation	Another company already owns the workspace, or you do not need your own Tracker setup.	You create a personal account, receive an invite, accept it, and work inside that organization.

Company switching

A user can switch between organizations they belong to. Each organization has its own data context, so campaigns, sources, domains, reports, META assets, and member access can differ by company.

Check the active organization first

If a table looks empty or a module is missing, confirm the active organization before changing product settings.

Roles

Axalot uses three organization roles.

Admins manage organization settings, members, invitations, roles, and statuses. They can assign Admin, TeamLead, or Member roles.

TeamLeads can manage organization members only when the target user is a Member. They can invite Members and assign the Member role only.

Members use the enabled product modules in the active organization. They cannot manage organization settings, roles, invitations, or member statuses.

Role	Can manage settings	Can invite users	Can change roles	Can revoke access
`Admin`	Yes	Yes, any role	Yes, any role	Yes
`TeamLead`	No	Members only	Members only	Members only
`Member`	No	No	No	No

Keep one active Admin

Axalot protects the last active Admin. A role change, revoke action, or leave action is blocked when it would leave the organization without an active Admin.

Member statuses

Membership status controls whether a user has access or is waiting for action.

Status	Meaning
`Active`	The user has organization access.
`Invited`	A manager invited the user and the user has not accepted or declined yet.
`Requested`	The user requested access by organization slug and waits for approval.
`Rejected`	A request or invitation was declined or rejected.
`Revoked`	A manager removed access or cancelled an invitation.
`Left`	The user left the organization.

Status transitions

From	Allowed next status	Typical reason
`Requested`	`Active`	A manager approves the join request.
`Requested`	`Rejected`	A manager rejects the join request.
`Invited`	`Active`	The invited user accepts.
`Invited`	`Rejected`	The invited user declines, or a manager rejects it.
`Invited`	`Revoked`	A manager cancels the invitation.
`Active`	`Revoked`	A manager removes access.
`Active`	`Left`	The user leaves the organization.
`Rejected`, `Revoked`, `Left`	`Invited`	A manager invites the user again.

Create an organization

Open Console / Organizations.

Create the organization with a name and slug.

Axalot creates the organization and adds the creator as an Active Admin.

The new organization becomes the active console organization.

Join by organization slug

Users can request access to an organization by slug.

Enter the organization slug from Console / Organizations.

If the user already has an active membership, Axalot switches to that organization.

If the user has an invitation, accepting by slug activates the membership.

If no active membership or invitation exists, Axalot creates a Requested membership with the Member role.

Invite users

Invitations are managed from Console / Organizations / Members.

Open the organization members page.

Select Invite user.

Enter the email of an already registered Axalot user.

Select the role allowed by your own role.

Send the invitation. The membership becomes Invited.

Invites require registered users

Axalot invites existing registered users by email. If the email does not belong to a registered user, the invite is not created.

Change roles

Managers change roles from the organization members table.

Actor role	What can change
`Admin`	Any manageable member to `Admin`, `TeamLead`, or `Member`.
`TeamLead`	Member records to `Member` only.
`Member`	Cannot change roles.

Promoting a user to TeamLead or Admin requires confirmation. Inactive records with Rejected, Revoked, or Left status cannot change role.

Remove access

Removing a user from an organization means revoking the membership. It does not delete the user's Axalot account.

Open Console / Organizations / Members.

Find the member by email, role, or status.

Revoke the active membership or revoke a pending invitation.

The membership becomes Revoked, and the user no longer has access to that organization.

Revoked is not account deletion

Revoking access removes the user from the organization context only. It does not delete the global user account or erase organization history.

Leave an organization

A user can leave an organization from Console / Organizations. The membership becomes Left, organization data stays intact, and access is removed.

The last active Admin cannot leave until another active Admin exists.