Root user

"Identities" are now "Customers"

We used to refer to the representation of your customer in the Weavr system as an identity. We now just call them a customer. The two mean the same thing — you may still see identity in some API fields and older pages.

Every customer has exactly one root userRoot userThe individual who creates the customer. For corporates, the root user needs to be a legal representative of the company, such as a director or someone with power of attorney. For consumers, the root user is the customer. Every customer must always have one root user. - the user who registered the customer, and the user our financial providers hold accountable for it. The root userRoot userThe individual who creates the customer. For corporates, the root user needs to be a legal representative of the company, such as a director or someone with power of attorney. For consumers, the root user is the customer. Every customer must always have one root user. is created atomically with the customer, in the same API call.

Who the root user is

Customer	Root userRoot userThe individual who creates the customer. For corporates, the root user needs to be a legal representative of the company, such as a director or someone with power of attorney. For consumers, the root user is the customer. Every customer must always have one root user.
Corporate	A legal representative of the company - typically a director or someone with power of attorney.
Consumer	The consumer themselves.

The root userRoot userThe individual who creates the customer. For corporates, the root user needs to be a legal representative of the company, such as a director or someone with power of attorney. For consumers, the root user is the customer. Every customer must always have one root user.'s details are provided in the rootUser field of POST/corporates or POST/consumers.

Set up the root user

The root userRoot userThe individual who creates the customer. For corporates, the root user needs to be a legal representative of the company, such as a director or someone with power of attorney. For consumers, the root user is the customer. Every customer must always have one root user. can't be created on their own. It is created with the customer, then set up through the same steps for both customer types:

1. Create a corporate or consumer, including rootUser details.
2. Set up the root user: create a password, verify the email address, and enroll an authentication factor.
3. Complete KYB for a corporate or KYC for a consumer.

How the root user differs from other users

The root userRoot userThe individual who creates the customer. For corporates, the root user needs to be a legal representative of the company, such as a director or someone with power of attorney. For consumers, the root user is the customer. Every customer must always have one root user. is also an authorized userAuthorized UserAn individual that has been invited by the root user to manage a customer's instruments and transactions. They are not the legal owner of the customer but can be granted access to perform operations on its behalf. For corporates, card assignees are created as Authorized Users. US-English variant of _Authorised User_. of the customer, and authenticates and operates through the API the same way any other user does. The constraints below apply only to the root userRoot userThe individual who creates the customer. For corporates, the root user needs to be a legal representative of the company, such as a director or someone with power of attorney. For consumers, the root user is the customer. Every customer must always have one root user.:

• Always Admin. The root userRoot userThe individual who creates the customer. For corporates, the root user needs to be a legal representative of the company, such as a director or someone with power of attorney. For consumers, the root user is the customer. Every customer must always have one root user. is created with the Admin role, and this role can't be removed.
• Tied to due diligence. Identity verification (KYBKYB (Know Your Business). Know Your Business - the identity verification process for corporate customers. This process allows you to securely verify your business customer's identity. Weavr asks users to submit the information and documentation they need for approval by financial providers. for corporatesCorporates (Corporate Identity). Business entities that can be onboarded as customers on Weavr. Corporate customers represent companies and require Know Your Business (KYB) verification. They can have multiple authorised users and issue cards to card assignees., KYCKYC (Know Your Customer). Know Your Customer - the identity verification process for consumer customers. This process allows you to securely verify your user's identity. Weavr asks users to submit the information and documentation they need for approval by financial providers. for consumersConsumers (Consumer). Individual people who can be onboarded as customers on Weavr. Consumer customers require Know Your Customer (KYC) verification. For consumers, the card owner and card assignee are typically the same person.) is performed in the root userRoot userThe individual who creates the customer. For corporates, the root user needs to be a legal representative of the company, such as a director or someone with power of attorney. For consumers, the root user is the customer. Every customer must always have one root user.'s name. The root userRoot userThe individual who creates the customer. For corporates, the root user needs to be a legal representative of the company, such as a director or someone with power of attorney. For consumers, the root user is the customer. Every customer must always have one root user.'s email must be verified before due diligence can start.
• Singular. A customer always has exactly one root userRoot userThe individual who creates the customer. For corporates, the root user needs to be a legal representative of the company, such as a director or someone with power of attorney. For consumers, the root user is the customer. Every customer must always have one root user.. Other users can be added later, but the root userRoot userThe individual who creates the customer. For corporates, the root user needs to be a legal representative of the company, such as a director or someone with power of attorney. For consumers, the root user is the customer. Every customer must always have one root user. can't be replaced or unset.

Any other users are added later through customer access management and can have any combination of roles.

Identifying the root user in your app

The user object returned by the API doesn't include a rootUser flag. Record the root userRoot userThe individual who creates the customer. For corporates, the root user needs to be a legal representative of the company, such as a director or someone with power of attorney. For consumers, the root user is the customer. Every customer must always have one root user.'s id when you create the customer, and store it alongside the customer in your own system - for example, to scope access controls or admin UI in your product.