Portal profiles
Restrict setup providers and features, require configured attribute mappings, and finish a profile-backed link.
A portal profile is an environment-owned setup preset. It names the allowed identity providers, allowed features (sso and dsync), and required attribute keys. The portal API enforces these restrictions on each action. Provider IDs come from the portal catalogue; they identify selectable provider configurations, not a verified issuer.
Business and Enterprise environments can create or replace profiles and attach them to new links. Each environment can have up to 20 profiles. Manage them through GET and POST /, and GET, PUT and DELETE /. Attach a profile when creating a portal link.
These are backend API capabilities. The portal frontend does not yet implement profile selection or the Finish workflow.
Required mappings
Section titled “Required mappings”Required keys can come from the fixed attribute catalogue or the environment’s custom definitions. Completion checks the current configuration separately for every selected feature: if both SSO and directory sync are selected, each must cover every required key.
Built-in automatic mappings count. A custom key needs an explicit mapping for that feature. A value observed during a test sign-in does not satisfy the requirement. Missing-key refusals identify the keys for each affected feature. Directory sources do not support every fixed attribute: manager_email and employment_start_date are not supported fixed sources. The groups requirement checks membership-source configuration.
A custom definition required by a profile cannot be deleted. Deleting a profile referenced by an unexpired link is also refused.
Finish this link
Section titled “Finish this link”When the IT admin finishes a profile-backed setup in the portal, the portal submits the selected features and their organization-owned connection or directory. A pinned link can select only its connection. The server checks the current profile, resource scope and configured mappings, then records one audited completion for this link.
Repeating the same completion returns its original scope and timestamp. Concurrent requests cannot create multiple completions. A different completion does not replace the stored result. An expired unfinished setup completes nothing.
After completion, this link cannot edit resources. Later profile edits do not change its stored completion, existing connections or sign-ins. Before completion, profile edits apply to the next action. The authenticated portal context exposes current profile_configuration only while setup is unfinished; it contains requirements, not mapping sources or attribute values.
Existing setups and plan changes
Section titled “Existing setups and plan changes”Links without a profile keep their existing behavior; the new Finish operation requires a profile-backed link. Downgrading a plan does not remove restrictions from existing unfinished setups or interrupt existing connections and sign-ins. Creating or replacing profiles and attaching them to new links below Business returns plan_limit_reached.
See the management reference for request fields and refusal codes.