- A project contains the resources you build with: token collections, user wallets, API keys, billing information, and more.
- An organization contains one or more projects, plus the members, roles, and security settings that apply to all of them.
Personal and Team Organizations
Every account starts with a personal organization. It is your own space, you are its only member, and it never changes hands. A team organization is the one you create to work with other people. Create it from the organization menu in the console, name it, and invite your teammates. You can belong to several organizations at once, for example your own and your employer’s, and switch between them from the same menu. Each organization keeps its own projects, and the project list in the sidebar always shows the organization you are in.Organizations follow the environment boundary described in Staging vs Production: an organization in staging and an organization in production are separate, each with its own members, invitations, and authentication setup.
Roles
Each member holds one role in each organization. The same person can be an admin in one organization and a developer in another.
Developer is the least privileged role and the default for a new invitation. Ownership is never handed out as a role: an organization has exactly one owner at a time.
Project Access Follows the Organization
Every member of an organization has access to all of its projects; there are no per-project invitations. Adding someone to the organization grants that access, removing them revokes it, and their organization role decides what they can do in each project. Admins and owners can also manage who is listed on a project. A project can additionally be shared with someone outside the organization. That person is listed on the project itself, with a Developer or an Admin role, and sees only that project. The Members tab of a project therefore shows two kinds of rows:- Members of the organization: they have access to the project through the organization. Change their role or remove them in the organization settings, not on the project.
- Members listed on the project: shared with this project alone. Change their role or remove them on the project.
A member of the organization can also be listed on a project itself, and that row decides what they can do there: an admin of the organization listed as a developer on a project is a developer in that project.
A project stays in the organization it was created in. To move one, contact Crossmint support.
Invitations
Admins and owners invite people by email address from the members section of the organization settings, and pick the role each one starts with.- The invited person does not need a Crossmint account yet. The email links to the console, where they sign in or create the account that accepts the invitation.
- A pending invitation waits in the organization menu of the person invited, so they can accept it whenever they next sign in.
- Admins and owners resend or revoke a pending invitation from the same members section.
MFA and SSO support
Crossmint offers extra authentication features to enterprise organizations: two-factor authentication with an authenticator app (TOTP), and single sign-on through your own identity provider.Enterprise feature. Contact us for access.
Ownership
A team organization has exactly one owner, and only the owner transfers ownership, from the members list. The member who receives it becomes the owner, and the previous owner stays in the organization as an admin. A personal organization cannot be transferred.See Also
Project and Team Management
What a project holds, and the privacy policy it needs to show user data
Staging vs Production
Why your staging and production accounts are entirely separate
API Keys Overview
The keys a project issues, and the scopes they carry
Account Verification
Verifying your account before going live in production