Configure Platform options, branding and ServiceHub tiles
Tenant administrator or the delegated permissions for the particular Setup action. Some capabilities also require module activation and the applicable operating view.
Platform settings consolidate tenant operating options and presentation. They are distinct from the cross-tenant platform-admin console. The historical standalone Customize navigation was merged into Platform.
Before you start
Confirm the intended tenant, required modules and authorized administrator. Record the current setting and downstream consumers before changing operating behaviour or portal entry points.
Steps
- Open Settings → Platform and select ITSM Lite or CSM Full as appropriate for the maintained service information.
- Review available CSM switches independently: Service Instances, CI relationship graph, automatic impact analysis, availability propagation, multiple Change targets, CAB and environment-specific Offerings.
- Verify necessary module activation with the platform administrator and validate relevant data before enabling a feature. The documented Boolean defaults are false.
- Upload the approved tenant logo in the customization area, respecting the documented 2 MB limit and supported image validation. Check appearance in the workspace and tenant login context.
- Configure ServiceHub landing tiles and their order: Incident, Catalog Item, Request for Information and All Catalog Items.
- Test each tile as a normal user to confirm the intended in-portal action and permitted routing.
- Review tenant currency where exposed; the documented ISO currency default is EUR. Validate financial display without assuming amounts were converted.
Identity & SSO configuration
The platform administrator must grant an enabled Identity & SSO feature and an ACTIVE, unexpired module licence before the tenant administrator can use Platform → Identity & SSO — Microsoft Entra ID. In that tab, the tenant administrator saves a directory connection, maps groups, applies it in PILOT, completes membership/removal tests, and explicitly activates or disables it. This is not the same as turning on the platform-level module. Under an ACTIVE connection, Entra owns group names and membership, while DockPilot's optional Team management fields remain editable. A PILOT protects its mapped teams. Existing sign-in connections are not automatically disabled when the module licence expires.
View and module boundaries
Switching back to ITSM Lite does not delete existing CI/Instance data; applicable technical choices stop being consulted while disabled. Enabling CSM Full does not create topology, establish data quality or activate every optional module.
Portal and branding behaviour
An Incident tile's configured team override is resolved server-side from the selected tile. A normal user cannot obtain arbitrary routing by submitting an untrusted team ID.
The tenant logo is used for unauthenticated login branding and is served through the tenant realm context. Use approved public-facing artwork and verify the correct realm if branding is missing.
Templates and currency
Default-status seeding and catalog/landing-tile template snapshot workflows are distinct. No universal clone-all-Settings import/export is established. Resolve references and review scope before applying any available template.
Changing display currency does not establish foreign-exchange conversion, historical value migration or an accounting process.
Expected result
The tenant presents appropriate entry points and branding, while technical features use deliberate, tested settings.
Important behaviour
A feature switch is not a maturity score, dependency discovery or proof of measured availability. Exact controls can depend on tenant release, enabled modules and rights. Keep platform-admin provisioning and module activation separate from tenant-local presentation.