Project policies are now generally available, providing granular permission control at the project level. Administrators can define specific Allow/Deny rules for roles within a project, giving you precise control over what actions users can perform in Uniform.

With project policies, you can configure permissions per role, per project, covering all aspects of the Uniform platform from content management to experience modeling and optimization. This enables you to create custom access control patterns that match your team's workflow and security requirements.

Granular targeting

For compositions, entries, and patterns, project policies support granular targeting criteria:

• By type: Target all entities of a specific composition type, content type, or component type
• By pattern: Target entities that match a specific composition pattern, component pattern, or entry pattern
• Specific entities: Target individual compositions, entries, or patterns by selecting them directly

This granular targeting enables use cases like restricting editors to only specific content types, enforcing creation of compositions based on composition patterns instead of allowing free-form creation, restricting who can manage patterns, or protecting critical content from unauthorized changes.

CLI support

Project policies can be managed programmatically using the Uniform CLI. The policy-documents commands allow you to pull, push, and sync policy documents across projects, making it easy to maintain consistent permissions across development, staging, and production environments.

Getting started

• For comprehensive guidance on project policies, see the project policies documentation.
• To understand how project policies fit into Uniform's broader access control system, see the roles and permissions guide.
• For some examples of common permission configurations, see the common scenarios guide.
• To manage policies programmatically, see the policy documents CLI commands documentation.