Global Packages
Global packages provide a standardized mechanism for promoting configuration changes from a source tenant to one or more target tenants while preserving consistency and reducing manual administrative effort. Within the Security application, global packages can contain user management configurations that are intended to be shared across environments or customer tenants.
Global packages provide a controlled deployment mechanism that supports these requirements:
- Deployment of common security configurations.
- Standardized access models across multiple environments.
- Maintaining consistency between development, test, staging, and production tenants.
- Reducing manual configuration effort.
- Ensuring governance and auditability.
Security resource use case examples
The Security application contains several resource types that may participate in global package deployment scenarios.
Security roles
Security roles define permissions that can be assigned to users. These are common use cases:
- Deploying standard administrator roles.
- Maintaining consistent permission structures.
- Promoting role updates between environments.
Functional security roles
Functional security roles define access to application capabilities and business functions. These are common use cases:
- Standardizing application access.
- Supporting enterprise security governance.
- Maintaining role consistency.
Security access profiles
Security access profiles define contextual access restrictions and security controls. These are common use cases:
- Standardizing login hour restrictions.
- Standardizing idle-session timeout override restrictions.
- Maintaining consistent security policies between tenants.
Groups
Groups provide logical user associations used for administration and access assignment. These are common use cases:
- Standardized onboarding groups.
- Regional groups.
- Departmental group structures.