Who is acting?
What can they do?

Choose the authentication approach for the request, then apply permissions and customer context to the operation.

Identity, context, permission
Authenticated personWho is acting?
Selected customerFor which business?
Authorized operationWhat can they do?
Privileged integration keys stay on the server.
01

Administrator integrations

An administrator API key inherits the permissions of its linked administrator. Use a deliberate integration account and keep the key in the server environment.

02

Customer-facing identity

Use the supported OAuth2 sign-in approach for a customer application. Authentication identifies the person; it does not replace the customer membership and authorization checks.

03

Authorization is a separate step

Resolve the permissions required for a read or action. A signed-in person should only operate within the customer contexts and capabilities they are allowed to use.

04

Design for denied access

Make a permission failure understandable in the interface. Avoid retrying a denied operation as if it were a transient network failure.

Let’s talk about
your next project.

Three quick questions to start the conversation.

What’s your name?
Your email app opens a draft at the final step. Nothing is sent automatically.