Organizations
An organization is your company’s space in almyty: its assistants, connected systems, keys and people all live there, separate from every other organization. Inside it you invite colleagues, give each one a role, and group people into teams. For example, the support team can manage its own assistants while sales sees only theirs, and an intern can look around without changing anything.
Your first organization
When you sign up, your first organization is created for you from the name you enter.
To create another one:
- Open Organizations.
- Click Create organization.
- Enter a name and, if you like, a description, then click Create organization.
- You are its owner. Its details, members and settings are on its page.
To switch between organizations, click the organization selector near the top of the sidebar and pick one. Every page then shows that organization’s things.
Invite people
Open Settings → People and access → Members and teams.
- Click Invite member.
- Enter their email address.
- Pick a role: Member or Admin.
- Click Send invitation.
They get an email with a link. If they have no account yet, the link takes them to sign up with the invitation already attached. Invitations not yet accepted are listed under Pending invites, where you can cancel one.
Change someone’s role: open the organization’s page on Organizations, open the menu on the person’s row and pick Change role (Viewer, Member, Admin or Owner). Only owners and admins can change roles.
Remove someone: click the remove button on their row and confirm Remove member. They lose access at once. What they created stays, and anything they kept private moves to you.
Roles
| Role | What they can do |
|---|---|
| Owner | Everything, including deleting the organization and handing over ownership. One per organization. |
| Admin | Manage people, everything in the organization, and settings. Cannot delete the organization. |
| Member | Create and manage their own things, run assistants and use tools. |
| Viewer | Look at everything shared with the organization, but not create, change or delete anything. |
| Action | Owner | Admin | Member | Viewer |
|---|---|---|---|---|
| See what’s shared with the organization | Yes | Yes | Yes | Yes |
| Create things | Yes | Yes | Yes | No |
| Change their own things | Yes | Yes | Yes | No |
| Change things shared with the organization or a team | Yes | Yes | No | No |
| Manage people | Yes | Yes | No | No |
| Manage teams | Yes | Yes | No | No |
| Change settings | Yes | Yes | No | No |
| Delete the organization | Yes | No | No | No |
Roles never reach into someone else’s private things (Only you) (see below).
Teams
Teams are groups of people inside an organization, such as Support or Sales, so each team can have things only it sees. Every organization starts with an Everyone team that every member belongs to. It can be renamed but not deleted.
To create a team:
- In Settings → People and access → Members and teams, find the Teams card.
- Click Create team.
- Enter a name and, if you like, a description.
- Add people from the organization, each as a Member or a Lead.
A team Lead manages who is in the team, can rename it, manages the things shared with the team, and can approve requests from the team’s assistants. A team Member can use what’s shared with the team but not manage it.
Who can see what
Assistants, tools, APIs, gateways, runners, credentials and AI provider connections each have a Who can use it setting:
- Only you: only the person who made it can see or use it. This holds even for the organization’s owners and admins.
- Everyone: everyone in the organization.
- One team: only the members of one team.
A private tool, API or assistant cannot be attached to something shared more widely, which would expose it through the back door. Share it first, or keep both private to the same person. An assistant private to its owner cannot be published on a channel, because the people who reach it through a channel have no almyty account: share it with the organization first.
You can only put something in a team you lead. Owners and admins can put things in any team.
Putting something in the Everyone team is not quite the same as sharing it with the organization: today every member is in Everyone, but if you remove people from that team, they lose access.
For developers
Visibility values are visibility='private', visibility='org' and visibility='team' (with a teamId). Private is enforced by the backend, not only hidden in the UI. Visibility, not the absence of a teamId, decides access: private resources have no team, team resources require one, and a resource with no visibility value is treated as org-wide. Team roles are stored as team_admin (shown as Lead, TeamRole.LEAD) and team_member (shown as Member); org owners are added to Everyone as team_admin, other roles as team_member.
Organizations live at /organizations, /organizations/new and /organizations/:id.
| Caller role | Resource visibility | Read/Use | Manage |
|---|---|---|---|
| Resource owner | own private | Yes | Subject to the action’s normal role checks |
| Anyone else, including org owner / admin | another user’s private | No | No |
| Org owner / admin | org or team | Yes | Yes |
| Org member (no team) | org | Yes | requires explicit org-level permission |
Org member, team_admin of the resource’s team | team | Yes | Yes |
Org member, team_member of the resource’s team | team | Yes | No |
| Org member, not in the resource’s team | team | No | No |
Organization, member and team management is available over REST; only the owner can delete an organization, which permanently removes everything in it. See the API reference.