For the complete documentation index, see llms.txt. This page is also available as Markdown.

Assign Role Permissions

Membership.

A contact (user) is a person in your project's membership directory, with one or more linked logins (identities). Membership manages their profile, identities, roles, and lifecycle.

Assigns the role permissions.

Membership

put
Authorizations
HTTPRequired

JWT Bearer Authorization

Path parameters
versionstring Β· nullableRequired

The CodeMash API version used to fetch data from the API. If not specified, the last version will be used. E.g.: v3

Body

Membership

correlationIdstring Β· nullableOptional

CorrelationId for each request

cultureCodestring Β· nullableOptional

Specify culture code when your response from the API should be localised. E.g.: en

timeZoneIdstring Β· nullableOptional

TimeZone

envstring Β· nullableOptional

Target environment for this request (e.g. TEST, STAGING). Optional β€” when omitted the request runs against PROD. Can be passed in a header as norbix-env.

projectIdstringRequired

ID of your project. Can be passed in a header as norbix-project-id.

databaseIntegrationIdstring Β· nullableOptional

Database integration id. Optional β€” defaults to the request environment's default integration.

idstringRequired

Id of the user login to assign roles to, from get_users.

rolesstring[] Β· nullableOptional

The complete new list of role names (full replacement), from get_roles.

Responses
200

OK

application/json
put/{version}/membership/auth/assign-roles
200

OK

In the dashboard

Manage this visually in Norbix Cloud β€” see Membership β†’ Users.

Use it from code

Every Norbix SDK exposes this endpoint as a method β€” see Assign Role Permissions in the SDK reference, with examples in every language.

Last updated