Author and Admin Identity & Access Control
Done
#3387
Story Statement
As a platform administrator, I want secure authentication, role-based authorization, and admin-controlled user provisioning so that access is consistently enforced and governed for all role types.
Business Value
- Strengthens security and governance of role access.
- Reduces operational risk from misconfigured permissions.
- Improves compliance readiness through controlled access.
Acceptance Criteria
- Given users authenticate, when credentials or federation checks pass, then access is granted according to policy.
- Given external and internal users access the system, when authentication is evaluated, then controls apply consistently.
- Given an admin creates or updates users, when changes are saved, then permissions take effect correctly.
- Given administrative boundaries are defined, when non-admin users attempt admin actions, then access is blocked.
- Given multiple role types are configured, when users are assigned roles, then access matches role definitions.
- Given role scopes vary by workspace or product, when permissions are evaluated, then scope rules are enforced.
- #Feature test
- Ask a admin (Aleido right now) to give a user **Stake holder access**. (result should be "read only") Validate that as a Stake holder I cannot edit or change objects
- Ask a admin (Aleido right now) to give a user **Author access.** Validate that as a Author I can edit and change objects
Configurable Metadata Taxonomy and Multi-Level Application
Done
#3395
Story Statement
As a metadata manager, I want configurable metadata taxonomies (domains and values) and multi-level metadata assignment so that taxonomies can evolve and be applied consistently across recipe, topic, and element levels.
Business Value
- Improves content filtering and precision in delivery channels.
- Supports scalable taxonomy management across products.
- Increases downstream automation through richer metadata context.
Acceptance Criteria
- Given metadata taxonomies are maintained, when administrators update taxonomies, then updates can be added without schema breakage.
- Given evolving business needs, when taxonomy changes occur, then existing content remains manageable.
- Given content at multiple structural levels, when metadata is applied, then level-specific metadata is supported.
- #Feature test
- Validate that meta data can be applied on object level
- Validate that meta data can be applied on version level