在此页面上:了解默认忠诚度角色、可用权限、角色权能、沙盒范围以及如何向用户分配角色。
概述 overview
Adobe Journey Optimizer忠诚度使用Adobe Admin Console基于角色的访问控制(RBAC)来管理用户访问权限。
必须先分配角色,用户才能执行忠诚度操作。 拒绝未分配角色的用户访问忠诚度服务端点。 在将用户引导至忠诚度之前,为将使用该服务的每个用户分配适当的角色。
角色可以直接分配给单个用户,也可以通过用户组进行分配。 了解如何将角色分配给用户。
推荐的角色 recommended-roles
忠诚度提供为 Prod 沙盒预配置的三个默认角色。 新客户可以按原样使用这些角色。
忠诚度管理员 loyalty-administrator
忠诚度管理员角色提供对所有忠诚度功能的完全管理访问权限:挑战、配置、产品目录和见解。
忠诚度从业者 loyalty-practitioner
忠诚度从业者角色专为管理整个挑战生命周期并编辑主要配置的业务所有者设计。 奖励配置、事件配置和产品目录访问均为只读。 不允许删除和高级配置写入。
忠诚度分析师 loyalty-analyst
忠诚度分析师角色提供对挑战、产品目录和见解的只读访问权限。 使用此角色进行报告和审核。
角色权能 role-capabilities
默认角色范围 default-role-scope
要授予用户访问非生产沙盒的权限,例如暂存或开发沙盒,请为该沙盒创建自定义角色,并分配与相应默认角色相同的权限。
自定义角色的可用权限 custom-role-permissions
当您为非生产沙盒创建自定义角色时,请从以下权限中选择。 要复制默认角色,请参阅上面相关角色部分中列出的权限。
向用户分配角色 assign-roles
Adobe Admin Console支持两种将角色与用户关联的方法。
将用户直接分配给角色 assign-users-directly
将个人用户直接添加到角色。 这种方法最适合小团队或一次性任务。
使用用户组 use-user-groups
创建用户组,然后将用户和角色分配给该组。 此方法最适合按部门或职能大规模管理访问。
有关管理角色、组和用户的分步说明,请参阅Adobe Journey Optimizer访问控制文档:
访问疑难解答 troubleshooting
如果用户无法访问忠诚度挑战或相关功能,请检查以下内容:
- 用户已分配给忠诚度角色。
- 角色包括启用了忠诚度挑战的沙盒。
- 角色包含用户尝试执行的操作所需的权限。
- 对于非生产沙盒,已为该沙盒创建自定义角色。
- 针对忠诚度挑战启用了组织和沙盒。
如果在更新权限后访问问题依然存在,请联系您的Adobe代表。
This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.
For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.
- TL;DR: This page explains the default Loyalty Challenges roles, available permissions for custom roles, role capabilities, sandbox scope, how to assign roles to users, and how to troubleshoot access issues.
Intents:
- Identify the three default Loyalty roles and what each one permits.
- Compare role capabilities across Challenges, primary organization configuration, reward configuration, event configuration, product catalog, and insights.
- Understand that default roles are scoped to the Prod sandbox and create a custom role for other sandboxes.
- Select permissions when building a custom role for a non-Prod sandbox.
- Assign roles to users directly or through user groups.
- Troubleshoot why a user cannot access Loyalty Challenges or a related feature.
Glossary:
- Loyalty Administrator: role providing full administrative access to all Loyalty features: challenges, configuration, product catalog, and insights (product-specific)
- Loyalty Practitioner: role for business owners who manage the full challenge lifecycle and edit primary configuration; reward configuration, event configuration, and product catalog access are read-only; deletion and advanced configuration writes are not permitted (product-specific)
- Loyalty Analyst: role providing read-only access to challenges, product catalog, and insights, for reporting and audit purposes (product-specific)
- Manage Loyalty Advanced Configuration: permission to manage reward endpoints and event transformation settings, including read/write access to sensitive credential values (product-specific)
- Develop Loyalty Challenges: custom-role permission to create and edit challenges via API; delete and lifecycle actions are not permitted (product-specific)
Guardrails:
- Role assignment is required before users can perform Loyalty operations.
- Users without an assigned role are denied access to Loyalty service endpoints.
- Default Loyalty roles (Loyalty Administrator, Loyalty Practitioner, Loyalty Analyst) are scoped to the Prod sandbox only.
- Primary organization configuration deletion is permitted for Loyalty Administrator only, not for Loyalty Practitioner.
- Reward configuration write access or access to sensitive values, and event configuration write access, are permitted for Loyalty Administrator only.
- Product catalog import or edit, and insights write or KPI configuration update, are permitted for Loyalty Administrator only.
- Loyalty Analyst has no create, edit, delete, publish, unpublish, archive, or journey-generation-trigger access to Challenges.
Prerequisites and permissions:
- To grant users access to a non-Prod sandbox (such as staging or development), create a custom role for that sandbox and assign the same permissions as the corresponding default role.
- Only Product administrators and System administrators can manage users, groups, and roles.
Terminology:
- Canonical names: Loyalty Administrator, Loyalty Practitioner, Loyalty Analyst — the three default Loyalty roles.
- Do not confuse: “Manage Loyalty Primary Configuration” (create, edit, and delete) ≠ “Configure Loyalty Primary Configuration” (create and edit; deletion is not permitted).
- Do not confuse: “Manage Loyalty Challenges” (full challenge operations including delete, publish, unpublish, archive, and trigger journey generation) ≠ “Develop Loyalty Challenges” (create and edit via API only; delete and lifecycle actions are not permitted) ≠ “View Loyalty Challenges” (view only).
- Do not confuse: “Manage Loyalty Insights” (view, update KPI configuration, trigger the insights pipeline) ≠ “Develop Loyalty Insights” (view insights data and update insight cards) ≠ “View Loyalty Insights” (view AI-generated insight cards, health vitals, and challenge performance data only).
FAQ:
- Q: What are the three default Loyalty roles? — Loyalty Administrator, Loyalty Practitioner, and Loyalty Analyst.
- Q: What sandbox are default Loyalty roles scoped to? — The Prod sandbox only.
- Q: How do I give a user access to a non-Prod sandbox? — Create a custom role for that sandbox and assign the same permissions as the corresponding default role.
- Q: Can a Loyalty Practitioner delete primary organization configuration? — No, deletion is not permitted for Loyalty Practitioner.
- Q: Who can manage users, groups, and roles? — Only Product administrators and System administrators.
- Q: What access does a Loyalty Analyst have? — Read-only access to challenges, product catalog, and insights, for reporting and audit purposes.
Troubleshooting:
- Symptom: user cannot access Loyalty Challenges or a related feature. Checks: the user is assigned to a Loyalty role; the role includes the sandbox where Loyalty Challenges is enabled; the role includes the permission required for the action; for non-Prod sandboxes, a custom role has been created for that sandbox; the organization and sandbox are enabled for Loyalty Challenges. If issues persist after permissions are updated, contact your Adobe representative.
Best practices:
- Assign users directly to a role for small teams or one-off assignments.
- Use user groups to manage access by department or function at scale.
Related pages:
- For step-by-step instructions on managing roles, groups, and users: Manage users and roles (administration/permissions.md)
- For step-by-step instructions on managing roles, groups, and users: Built-in permissions (administration/ootb-permissions.md)
Personas:
- admin: Can assign a role to users directly, or create a user group and assign both users and a role to the group. Can create a custom role for a non-Prod sandbox and assign it the same permissions as the corresponding default role. The page states that default Loyalty roles are scoped to the Prod sandbox only. Where: “Assign roles to users”.
Onboarding:
- Level: Intermediate
- First minimal step: Assign an appropriate role to each user who will use the service.
- Success check: The assigned user can perform Loyalty operations and is not denied access to Loyalty service endpoints.
- Next: For step-by-step instructions for managing roles, groups, and users: Manage users and roles (administration/permissions.md); For built-in permissions details for managing roles, groups, and users: Built-in Roles (administration/ootb-permissions.md)