General
User custom fields is an organization-wide setting owned by a single team, the team that ingests users for your organization. On other teams the toggle is disabled and names the owning team. Turn it off there first to change ownership.
Access
Access configuration in promotions
When promotions are enabled, you can promote access configuration between linked teams. The comparison includes resources and roles created in Serval, ingested roles with request settings, an access-policy override, custom provisioning workflows, form confirmation, or owners, and the linked prerequisite roles and parent resources they need. Review each selected role’s settings, including prerequisites. Applying a promotion copies its request settings, owners, access-policy override, and provisioning method. A source role without a policy override clears the destination override. Existing ingested resources and roles keep their provider-managed names, descriptions, and external identifiers. Missing ingested resources and roles can be created by a promotion. Matching uses the same integration identity and external resource identifier; roles match by parent resource and role name. Promotions don’t translate between separately identified integration tenants or copy users’ access grants. Later ingestion adopts matching records and preserves their configured access settings. A full resource sync can still remove resources that no longer exist in the provider’s results.Team links and promotions
Where promotions are enabled, Team Links shows why each connection exists: Manual, Pipeline, or Branch. Each direction between two teams has one connection. Revoking a Manual connection stops promotions in that direction. The reverse connection is independent. Pipeline and Branch connections are managed by their related environment or branch and cannot be revoked individually. Existing connections without a recorded origin remain Manual. A source team’s Builder or Manager can propose configuration through an authorized outgoing connection. Applying the promotion requires authorization on the receiving team. A connection does not give a Builder permission to manage connections or apply changes to the receiving team. Receiving-team members can open reviews shared from the source team according to their review permissions.Ticketing
The Help Desk Agent settings include a Help Desk Agent Name field that overrides your organization’s agent name for this team’s replies, prompts, and notifications. Leave it blank to inherit the org-wide name. An org admin must first enable per-team agent names in Admin settings.
Infrastructure
Quick reference (team)
For org-wide tasks (invite users, create teams, SSO, API keys), use the table in Organization settings and security.