Skip to main content
An organization contains members and projects. Each project isolates API keys, usage, logs, model access, and limits. Project-level roles provide narrower access for project owners, developers, key managers, usage viewers, and viewers.

​
How access is decided

A person can hold a role on the organization, on a project, or both. An action is allowed if either role grants it, so a project role can give someone access to one project without giving them the whole organization. New accounts start with an organization and a default project, and the creator becomes the organization owner and the project owner.

​
Organization roles in detail

​
Project roles in detail

​
Invite people

Invite a teammate by email from Projects or the organization settings. The invitation is a link that the person accepts while signed in to Mibyan. Give the least-privileged role that lets them do the job, for example Key manager for someone who only rotates keys.
Create a service account for each application and give it a key, instead of sharing a person’s key between services.