Technologie & IA
Alchemy separates organization and team permissions in its dashboard
Following the November 17 announcement, Enterprise customers can group multiple teams under one organization, with separate permissions for billing, applications and API keys.

Three levels for organizing applications
On November 17, Alchemy announced the availability of organizations and role-based permissions in its Enterprise dashboard. The dashboard now places the organization above teams and their applications. A customer can bring several teams into one organization, for example to separate two products or assign development and production environments to different groups. The organization centralizes member management and usage visibility. Applications, keys and operational settings remain attached to teams.
An organization with at least two teams uses one plan, one payment method and one invoice. Alchemy says combined usage counts toward the plan's consumption. Administrators can see what each team used and set an organization-wide cap, a team cap or both. The documentation says reaching the organization-wide cap stops all teams, while reaching a team cap stops only that team.
Separate permissions for keys and billing
Alchemy defines three organization-level roles. Admin can create teams, manage members and handle billing. Its holders become admins of every team. Billing covers finance tasks and grants access to the plan and invoices. Member allows people to view the organization and join teams according to their assignments. Billing and Member on their own grant no access to applications or keys inside a team.
Within a team, Admin can manage members, settings and keys. Developer can see keys, configure applications and manage webhooks. Viewer can see applications, logs and configuration, with keys masked and no permission to make changes. The same person can therefore maintain an application in one team and follow another team's logs without gaining the same permissions in both.
Permissions to check when a role changes
Alchemy says invites and role changes appear in the activity log. The documentation describes a case that requires an extra check. If an organization admin becomes Billing or Member, they initially retain admin rights for every team. The interface flags this. An organization seeking to reduce those rights must then remove the relevant assignments or lower roles in each team. The organization role and team roles remain two separate items to check.
For customers already running separate teams, grouping them requires help from Alchemy's account team. The provider says members initially keep their current access and roles. This release does not offer custom roles or let customers define roles application by application. The change provides shared team management and a two-level division of permissions. Detailed permissions for an application still follow its team assignment.
