Organizations

Organizations are the top-level tenant boundary in almyty. Every resource — APIs, tools, gateways, agents, credentials, and LLM providers — belongs to exactly one organization. Users can belong to multiple organizations and switch between them.

Creating an Organization

When you sign up, your first organization is created automatically from the name you provide during registration.

To create additional organizations:

1. Navigate to Settings in the sidebar
2. In the Organization tab, scroll to the bottom and click Create Organization
3. Enter a name and optional description
4. You’ll be set as the owner of the new organization

Switching Organizations

Click the organization name in the sidebar footer (below the nav links). A dropdown shows all organizations you belong to. Click one to switch — all pages immediately scope to that organization’s data.

Managing Members

Navigate to Settings and open the Members & Teams tab.

Inviting members

1. Click Invite Member
2. Enter their email address
3. Select a role (owner, admin, member, or viewer)
4. Click Send Invite

The invitee receives an email with a link to accept. If they don’t have an account, the link takes them to the sign-up page with the invite pre-attached.

Changing roles

Click the role badge next to any member to change it. Only owners and admins can modify roles.

Removing members

Click the menu icon on a member row and select Remove. Removing a member revokes their access to all resources in the organization immediately.

Roles

Permission matrix

Teams

Teams are sub-groups within an organization for finer-grained access control. Every organization gets a default “Everyone” team on creation — every member is automatically a member of it. Org owners are added as team_admin (lead); other roles are added as team_member.

Resources (tools, agents, gateways, runners, credentials, APIs, LLM providers) can be created with one of two visibility settings:

• Org-wide (visibility='org') — visible to every member of the organization.
• Team (visibility='team', with a teamId) — visible only to members of that team.

When picking a team for a new resource, you can only park it in a team you’re team_admin (lead) of. Org owners and admins can park resources in any team.

Creating a team

1. In Settings → Members & Teams, open the Teams sub-tab
2. Click Create Team
3. Enter a name and (optional) description
4. Add members from the organization

The default “Everyone” team cannot be deleted (its delete button is disabled), but it can be renamed.

Team roles

Authorization model

The full picture, for a member acting on a resource:

Resources without teamId are treated as org-wide. The default “Everyone” team is not the same as org-wide — putting a resource in “Everyone” means every org member can see it (same effect today), but if you ever shrink the team’s membership it becomes a real boundary.

Via the API

Create an organization

curl -X POST /organizations \
  -H "Content-Type: application/json" \
  -d '{ "name": "Acme Corp", "description": "Production org" }'

List members

curl /organizations/{orgId}/members

Invite a member

curl -X POST /organizations/{orgId}/members \
  -H "Content-Type: application/json" \
  -d '{ "email": "dev@acme.com", "role": "member" }'

Update role

curl -X PATCH /organizations/{orgId}/members/{userId} \
  -H "Content-Type: application/json" \
  -d '{ "role": "admin" }'

Create a team

curl -X POST /organizations/{orgId}/teams \
  -H "Content-Type: application/json" \
  -d '{ "name": "Backend Team" }'

Delete an organization

Only the owner can delete an organization. This permanently removes all resources.

curl -X DELETE /organizations/{orgId}