Start by role

These recommended responsibilities are not fixed DAM roles. Actual permissions depend on license, functions, object scope, and policy. Separate drafting, review, and publication where practical.

The system administration quick start contains the canonical role-permission illustration. Names and selections there illustrate permission settings and membership, not a mandatory role template.

Platform administrator

Prepare organizations, accounts, permissions, workflows, schedules, and licenses.

1. Follow system setup.
2. Configure organizations and access, checking functions and data scope separately.
3. Maintain systems and sources, then hand harvesting to metadata administrators.
4. Configure approvals and scheduling.
5. Verify actual business-role visibility and actions rather than administrator results.

Data steward

Maintain business descriptions and coordinate standards, remediation, and asset information.

1. Verify datasets and fields and enrich names and descriptions.
2. Map published standards.
3. Review Intelligent Matching and standards validation.
4. Track issues and verification with remediation evidence.
5. Hand confirmed information to asset administrators for publication.

Standards administrator

Maintain definitions, codes, metrics, lifecycle, and field adoption.

1. Design catalogs, basic standards, and reference codes.
2. Review, publish, change, or retire through the lifecycle.
3. Maintain metric standards and dimensions; use Metric Management for mappings, queries, and monitoring.
4. Inspect actual field adoption through usage reports.

Quality administrator

Turn requirements into executable checks and close the remediation loop.

1. Create business and technical rules.
2. Test validation tasks on a small scope.
3. Assign issues, distinguishing execution success, closure, and verification.
4. Use quality reports for trends and inspect underlying details.

Security and asset administrator

Confirm ownership, visibility, classification, policies, publication, and usage controls.

1. Design catalog spaces and directory permissions.
2. Register and publish, then test ordinary-user visibility.
3. Define classification and levels, review and publish in the workbench.
4. Configure access policies and verify JDBC masking through the gateway.

Data consumer

Understand definitions and constraints, request a clear purpose and scope, and accept actual delivery.

1. Discover products.
2. Review definition, owner, quality, and security; request browsing access if details are unavailable.
3. Submit and track requests.
4. After approval, coordinate offline delivery and verify approved scope. Approval records are not files, database accounts, or API authorization.

Use end-to-end scenarios to coordinate multiple roles.