Organizations
An Organization is the highest-level entity in Axoria. All projects, members, settings, permissions, and data are tied to an organization. Without an organization, it is not possible to create projects or collaborate with others. After registering, you can create a new organization or join an existing one via invitation.
Creating an Organization
Any authenticated user can create an organization.
- After registering/logging in, click Create Organization on the home screen.
- Enter the organization name (minimum 2 characters, maximum 100).
- The slug is auto-generated from the name (lowercase letters, numbers, and hyphens; 2-50 chars). The slug is immutable after creation and appears in organization URLs.
- Optionally add an avatar (built-in icon or image upload).
- Click Create to confirm.
You automatically become the Owner of the newly created organization.
Organization Profile
Where: Org Settings → General
| Field | Type | Rules |
|---|---|---|
| Name | Text | Max 100 chars. Required |
| Slug | Text | [a-z0-9-]{2,50}. System-unique. Immutable after creation |
| Description | Text | Max 500 chars. Optional |
| Logo | URL / Upload | Organization image shown in the header |
| Icon | String | Built-in icon key (FontAwesome), as an alternative to a logo |
| Status | Enum | ACTIVE, SUSPENDED, or DELETED |
Who can edit: members with the MANAGE_ORGANIZATION permission (Owner, Admin, or via Profile Group).
How it is enforced: All changes to the organization profile require the appropriate permission. Unauthorized requests are rejected with HTTP 403.
Organization Roles
Axoria has four organizational roles:
| Role | Permissions |
|---|---|
| OWNER | Full control: everything Admin can do + change plan + delete organization. Cannot be removed or have their role changed |
| ADMIN | Equivalent to Owner in operational permissions - manages members, projects, settings. Cannot delete the org or change the Owner's role |
| MEMBER | Access only to projects they've been added to. No administrative access unless granted permissions via Profile Group |
| GUEST | Most restricted role. No default access to any project - only what is explicitly granted via a group or project |
How Permissions Are Decided
- OWNER → automatically has all
OrgPermissionvalues - ADMIN → automatically has all
OrgPermissionvalues - MEMBER / GUEST → has only the permissions assigned to the Profile Groups they belong to
Permission resolution is performed server-side on every request: the system iterates through the member's Profile Groups and checks whether any group grants the required permission. If no group grants it → access denied.
Organization Permissions (OrgPermission)
The permissions below are the only ones that can be assigned via Profile Groups:
| Permission | What it allows |
|---|---|
MANAGE_ORGANIZATION |
Edit the org's name, description, logo, slug, and general settings |
MANAGE_MEMBERS |
Add, remove, and change the role of org members |
INVITE_MEMBERS |
Send invitations to new members |
MANAGE_PROJECTS |
Create, edit, archive projects and configure any project in the org |
MANAGE_PROJECT_MEMBERS |
Control member access within any project |
MANAGE_BOARDS |
Configure boards and columns in any project |
MANAGE_ISSUE_TYPES |
Create and edit custom issue types in any project |
MANAGE_WORKFLOWS |
Configure workflows, statuses, and transitions in any project |
MANAGE_SETTINGS |
Access the organization's settings area (groups, plan) |
Important: Owner and Admin do not need any of these groups - they already have everything. Groups are used to grant granular powers to regular members.
Profile Groups
Where: Org Settings → Profile Groups
Profile Groups are named categories that group members together and share a set of permissions. They solve two problems:
- Bulk permissions: adding someone to a group automatically grants them all the group's permissions.
- Bulk project access: inviting an entire group to a project gives all its members the same project role.
Creating a Group
Who can create: members with MANAGE_SETTINGS (Owner, Admin, or via another group).
- Go to Settings → Profile Groups → + New Group
- Enter the name (unique per organization)
- Select the permissions group members will have
- Confirm
Editing a Group
A group's name and permissions can be edited at any time. Permission changes take effect immediately for all group members.
Deleting a Group
- System-created groups cannot be deleted.
- Deleting a group means members lose the permissions the group granted. Individual project access where they were directly added is not automatically removed.
Adding and Removing Members from Groups
Who can: members with MANAGE_MEMBERS.
- Adding a member to a group → they inherit the group's permissions immediately.
- Removing a member from a group → they lose the group's permissions, but do not lose access to projects where they were added individually.
Using Groups to Grant Project Access
When adding members to a project (at Project → Settings → Members), you can add an entire group instead of individual users. All group members receive the same project role.
Organization Members
Where: Org Settings → Members
Inviting a Member
Who can: members with MANAGE_MEMBERS or INVITE_MEMBERS.
- Go to Settings → Members → + Add Member
- Enter the user's email address
- Select the role (
OWNER,ADMIN,MEMBER, orGUEST) - Optionally assign Profile Groups to the new member
- Click Send Invitation
The user receives an email with the invitation link. Upon accepting, they will have access to the organization with the defined role and groups.
Changing a Member's Role
Who can: members with MANAGE_MEMBERS.
Mandatory rules:
- The Owner's role cannot be changed by anyone - not even by another Owner.
- An Admin can change the role of Members and Guests, but not of another Admin or the Owner.
If the attempt is made → HTTP 403 FORBIDDEN.
Removing a Member
Who can: members with MANAGE_MEMBERS.
Mandatory rules:
- The Owner cannot be removed from the organization.
- Removing a member from the organization automatically revokes their access to all org projects.
- Issues assigned to the removed member are not automatically reassigned.
Updating a Member's Groups
Who can: members with MANAGE_MEMBERS.
You can add or remove groups from an existing member at any time via the action menu next to the member in the list.
Organization Projects
Where: Org Settings → Projects
The organization's project list is visible to any member. From this screen, authorized members can:
- Create new projects - requires
MANAGE_PROJECTSor being Owner/Admin - Check the status of existing projects (active, archived)
- Access project settings - requires
MANAGE_PROJECTS,PROJECT_ADMINin the project, or being Owner/Admin
Fields When Creating a Project
| Field | Type | Rules |
|---|---|---|
| Name | Text | Required |
| Key | Text | 2-10 chars, [A-Z0-9]. Immutable after creation |
| Description | Text | Optional |
| Type | Enum | SOFTWARE, BUSINESS, KANBAN, SCRUM, CUSTOM |
| Visibility | Enum | PRIVATE, INTERNAL, PUBLIC |
| Lead | UUID | User responsible for the project (optional) |
Plan and Billing
Where: Org Settings → Plan & Billing
Each organization is on one of four plans:
| Plan | Features |
|---|---|
FREE |
Limited projects and members; no advanced features |
STARTER |
Higher project and member limits; basic reports |
PROFESSIONAL |
Advanced reports, integrations, expanded storage |
ENTERPRISE |
No practical limits; dedicated support; SLA |
The current plan defines:
- Maximum number of active projects
- Maximum number of members
- Access to public reports (report tokens)
- Integrations and file storage capacity
To view or change the plan, go to Settings → Plan & Billing.
Danger Zone
Where: Org Settings → Danger Zone
Suspending the Organization
Suspending changes the organization's status to SUSPENDED. Suspended organizations:
- Remain accessible for the Owner to manage
- Block access for regular members
- Preserve all data in full
Who can: Owner only.
Deleting the Organization
⚠️ Completely irreversible. Deleting an organization permanently removes all projects, issues, sprints, members, settings, and associated files. This action cannot be undone.
Who can: Owner only.
Process:
- Go to Settings → Danger Zone → Delete Organization
- Confirm by typing the organization name in the verification field
- Click Delete Permanently
Full Summary - Who Can Do What
| Action | MEMBER/GUEST (no group) | MEMBER (adequate group) | ADMIN | OWNER |
|---|---|---|---|---|
| Create organization | ✅ (any user) | ✅ | ✅ | ✅ |
| View members list | ✅ | ✅ | ✅ | ✅ |
| Edit org profile | ❌ | MANAGE_ORGANIZATION |
✅ | ✅ |
| Invite members | ❌ | INVITE_MEMBERS |
✅ | ✅ |
| Manage members | ❌ | MANAGE_MEMBERS |
✅ | ✅ |
| Create profile groups | ❌ | MANAGE_SETTINGS |
✅ | ✅ |
| Manage groups | ❌ | MANAGE_SETTINGS |
✅ | ✅ |
| Create projects | ❌ | MANAGE_PROJECTS |
✅ | ✅ |
| Configure projects | ❌ | MANAGE_PROJECTS |
✅ | ✅ |
| Manage boards | ❌ | MANAGE_BOARDS |
✅ | ✅ |
| Manage workflows | ❌ | MANAGE_WORKFLOWS |
✅ | ✅ |
| Change Owner's role | ❌ | ❌ | ❌ | ❌ (nobody) |
| Remove Owner | ❌ | ❌ | ❌ | ❌ (nobody) |
| Suspend the org | ❌ | ❌ | ❌ | ✅ |
| Delete the org | ❌ | ❌ | ❌ | ✅ |
How Rules Are Enforced
All checks are performed in the backend, not the frontend:
| Scenario | System response |
|---|---|
| User without permission attempts an operation | HTTP 403 Forbidden |
| Unauthenticated user attempts an operation | HTTP 401 Unauthorized |
| Member attempts to change the Owner's role | HTTP 403 |
| Member attempts to remove the Owner | HTTP 403 |
| Member does not belong to the organization | HTTP 403 |
| User accesses a page without permission | Redirected to the error page |
The frontend hides buttons and menus for unauthorized actions, but all actual enforcement is done by the backend on every request.
Creating an Organization
- After signing up, click Create Organization.
- Enter the organization name (minimum 2 characters).
- Optionally add an avatar by dragging an image or clicking Select File.
- Click Create.
You automatically become the Owner of the newly created organization.
Organization Profile
In the organization settings panel you can:
- Change the name and slug
- Update the avatar (built-in icon or custom image)
- Add a description about the organization
Members
Inviting Members
To invite a new member:
- Go to Settings → Members.
- Enter the user's email address.
- Select the role to assign.
- Click Send Invitation.
The user will receive an invitation and, upon accepting, will have access to the organization with the assigned role.
Organization Roles
| Role | Description |
|---|---|
| Owner | Full control over the organization, members, projects, and billing. |
| Admin | Can manage members, projects, and general settings. |
| Member | Access to projects based on roles granted by Admins or Owners. |
Removing Members
An Admin or Owner can remove any member by going to Settings → Members and clicking Remove.
Note: The Owner cannot be removed from the organization by other members.
Profile Groups
Profile Groups let you organize members into named categories - like "Backend Team", "QA", or "External Partners". They simplify bulk access management for projects.
Creating a Group
- Go to Settings → Profile Groups.
- Click New Group and give it a name.
- Add members to the group.
Using Groups in Projects
When managing a project's members, you can add an entire group instead of individual members, granting all its members the same role at once.
Removing a member from a group does not automatically revoke their individual project access - it must be removed separately.
Plans and Limits
Each organization is on a plan that defines:
- Maximum number of active projects
- Maximum number of members
- Access to advanced features (public reports, integrations, storage)
To view or change the plan, go to Settings → Plan & Billing.
Deleting an Organization
⚠️ Irreversible action. Deleting an organization permanently removes all projects, issues, sprints, and associated data.
Only the Owner can delete the organization at Settings → Danger Zone → Delete Organization.