Skip to content

docs: capitalize Bearer in SCIM token format #6737

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ehcaw merged 1 commit into from
Jul 24, 2026
+1 −1
Merged

docs: capitalize Bearer in SCIM token format #6737

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion dashboard/scim.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@
In Okta, under **Applications**, click **Browse App Catalog** and search for **SCIM 2.0 Test App (Header Auth)**. This is Okta's standard integration for any SCIM 2.0 API that authenticates with a bearer token.
</Step>
<Step title="Add your Mintlify credentials">
Under the app's **Provisioning** settings, enter the Mintlify SCIM base URL and bearer token. Format the token as `bearer <token>`.
Under the app's **Provisioning** settings, enter the Mintlify SCIM base URL and bearer token. Format the token as `Bearer <token>`.
</Step>
<Step title="Enable provisioning actions">
Under **Provisioning to app**, enable the create, update, and deactivate options you want Okta to manage. Leave **Sync password** off, since Mintlify doesn't use Okta-managed passwords.
Expand Down Expand Up @@ -73,7 +73,7 @@

When a user belongs to multiple mapped groups, Mintlify assigns the highest-privilege role among them.

You can edit or remove a mapping at any time. This mapping is one-directional and only controls which Mintlify role a group receives. For example, suppose you map your identity provider's `developers` group to the editor role and later change that mapping to viewer. New members of `developers` become viewers in Mintlify, but the existing `developers` group itself is unchanged in your identity provider.

Check warning on line 76 in dashboard/scim.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

dashboard/scim.mdx#L76 

In general, use active voice instead of passive voice ('is unchanged').

## Rotate the bearer token

Expand Down