Skip to main content
Short answers about signing in, working across organizations, and what each role can do. For the full picture, follow the links in each answer to the canonical page.

Roles & permissions

What owners and admins can each do.

Org context

How X-Organization-ID picks which organization you act in.

Common questions

In the app, use the organization switcher to change which organization you are working in. From the API or an SDK, set the X-Organization-ID header (the organization’s UUID) on each request. See org context.
There are two roles: owner and admin. Owners manage billing and own the organization; admins can invite people, manage credentials, and build and run workflows, the AI Composer, and the Assistant. The member role has been retired, so there is no longer a read-only role. See roles & permissions.
A few older organizations may still show a leftover member value on some records. It is deprecated and not a role you can assign; treat owner and admin as the live roles.
ModuleX uses Clerk as its identity provider, so you sign in through Clerk. There is no separate ModuleX username and password. Your account and a starter organization are created on your first sign-in. See getting started.
No. API keys (they start with mx_live_) are shown only once when you create them and are not stored in a way that lets us show them again. Delete the old key and create a new one in Settings, then update wherever the old key was used. See authentication.
The organization you are calling is not one you belong to. This usually means X-Organization-ID is set to the wrong organization, or your API key is scoped to a different one. Set the header to an organization you are a member of. See org context.
Use Clerk’s sign-in and recovery options (password reset, single sign-on, and any other method your organization has enabled). If you still cannot get in after that, reach out through getting help.

Selecting your organization from code

Every organization-scoped request needs an organization. Send your API key in the Authorization header and the organization UUID in X-Organization-ID. The SDKs take the same two values when you create the client.
If you leave X-Organization-ID off an organization-scoped request, the API returns 400 with X-Organization-ID header is required. If it points at an organization you are not in, you get 403 with User is not a member of organization. See org context.

Keep reading

Organizations, roles & membership

How organizations, membership, and roles fit together.

Getting started — help

Signing up and making your first call.