Keep each team’s assistants to that team
For an organization where support, finance and IT all use almyty but shouldn’t all touch the same things. Each team gets its own assistants, APIs, gateways and keys, and the people in other teams can’t use them. A support agent can’t reach the finance team’s refund tools, and nobody has more access than they need.
What you need
- Owner or admin access to your organization.
- The Business plan, only if you want custom roles beyond the built-in ones (step 5).
How to build it
- Create the teams. Open Settings, then Members and teams. Under Create team, add one per group: Support, Finance, IT.
- Put people in them. Add members to each team as Member or Lead. A team’s lead can approve the requests of that team’s assistants.
- Set organization roles. Everyone also has an organization role: Owner, Admin, Member or Viewer. Keep Owner and Admin for the few people who run almyty for everyone.
- Give each thing an owner. When you create an assistant, an API, a gateway, a runner or a key, choose Who can use it: Only you, One team (pick the team) or Everyone. Finance’s refund tools and keys stay Team: Finance.
- Go finer if you need to. With the Business plan, Settings, Roles adds custom roles (for example “can run agents but not edit them”) and access rules that allow or deny specific actions.
Ideas
- Approval rules per team, so a finance request needs a finance approver: see Approval rules.
- With single sign-on, teams follow the groups in your company directory.
- Every access change is in the audit trail.