One person.
The right business context.

Make the selected customer explicit when your application supports people who belong to more than one business.

A person. Two customer contexts.
Jamie SmithSigned-in person
Selected customerNorthstar Studio
MembershipAuthorized member
Connected recordCustomer-scoped records
Requests use this customer context
01

Identity and customer are different

A person signs in with an identity. A customer record represents the business context they are working in. Membership connects the two.

02

Make switching visible

Show the active customer in your application. When the person switches, update the interface and subsequent requests to use that selected context.

03

Carry the context into requests

Use the supported customer path or X-Customer-Id context for the operation. Confirm the membership and permission requirements in your integration.

04

Keep records scoped

Orders, subscriptions, and custom application data should be presented for the selected customer. Handle a missing or unauthorized context before showing business information.

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.