Application Roles

Several predefined application roles for Oracle Content and Experience define what users can do. Some functionality is available only to users with specific application roles.

People can hold multiple application roles as needed. For example, you might want to designate one person as both a cloud account administrator and a service administrator. These application roles are assigned by the identity domain administrator. See Assign Roles to Groups and Assign Users to Groups.

Visitors can view certain sites, use public links, and view Oracle Content and Experience content embedded in apps or websites.

Any users that need to actually use Oracle Content and Experience must be assigned the standard user or enterprise user role in addition to any other roles they’re assigned.

The following table describes the application roles involved with Oracle Content and Experience instances with a Universal Credits subscription, a Government subscription, or a SaaS subscription. For information on how to access the interfaces listed in the table, see Administrative Interfaces.

Application Role (application role name in bold) Access and Actions Notes
Cloud account administrator Cloud account administrators use the Infrastructure Classic Console to perform the following actions:
  • Monitor and manage services for one or more Cloud accounts.
  • Create new users.
  • Provide access to services by assigning roles.
  • Upgrade or terminate subscriptions.

See Overview of Cloud Account Administration Tasks in Managing and Monitoring Oracle Cloud.

Cloud account administrators are set up when the account is created. They use their Oracle account to sign in to Oracle Cloud and access the Infrastructure Classic Console. If you need account administrator access and don’t have it, contact your primary account administrator. See Learn About Cloud Account Roles in Getting Started with Oracle Cloud.

If you want cloud account administrators to use Oracle Content and Experience and modify the service configuration, they must also be assigned the standard user or enterprise user role.

Service administrator (CECServiceAdministrator)

From the Oracle Content and Experience Administration: Settings interface:

From Oracle Content and Experience Administration: Integrations interface, configure integrations with:

From Oracle Content and Experience Analytics interface:

Service administrators must also be assigned the standard user or enterprise user role to be able to use Oracle Content and Experience.
Site administrator ( CECSitesAdministrator)

From the Oracle Content and Experience Sites page:

  • Create sites.

From the Oracle Content and Experience Developer page:

  • Create templates, components, and themes.

See Configure Sites and Assets Settings.

When using site governance, site administrators make approved templates available to users for creating sites, approve site requests, and manage sites. This role also applies if your service administrator configured Oracle Content and Experience to allow only site administrators to create sites, templates, or components.

Site administrators must also be assigned the standard user or enterprise user role to be able to use Oracle Content and Experience.

Developer (CECDeveloperUser)

From the Oracle Content and Experience Sites page:

  • Create, edit, and publish sites as long as this feature hasn’t been limited to site administrators.

From the Oracle Content and Experience Developer page:

Developers must also be assigned the standard user or enterprise user role to be able to use Oracle Content and Experience. Developers with the standard user role can create components, themes, and standard templates. Developers with the enterprise user role can also create layouts and save a site as a standard or enterprise template.
Content administrator (CECContentAdministrator) From the Oracle Content and Experience Administration: Assets page:
  • Create new content types and taxonomies and publish items.
Content administrators must also be assigned the enterprise user role to be able to use Oracle Content and Experience and access assets.
Repository administrator (CECRepositoryAdministrator) From the Oracle Content and Experience Administration: Assets page:
  • Create asset repositories.
  • Create localization policies.
  • Create publishing channels.

From the Oracle Content and Experience Analytics interface:

Repository administrators must also be assigned the enterprise user role to be able to use Oracle Content and Experience and access assets. A repository administrator is a user with a Manager role within at least one repository.
Standard user (CECStandardUser) From Oracle Content and Experience, standard users have access to:
  • Manage content (view, upload, and edit documents).
  • Share content and sites with others.
  • Use conversations to collaborate (discuss topics, direct message someone, assign flags to someone, add annotations to documents).
  • Manage groups.
  • Create, edit, and publish sites as long as this feature hasn’t been limited to site administrators.
  • View and interact with content items in sites.

  • Manage and view custom properties and edit values.
Any users that need to actually use Oracle Content and Experience must be assigned the standard user or enterprise user role. These roles aren’t assigned by default to any user.

See Task and Feature Comparison by Application Role.

Enterprise user (CECEnterpriseUser) From Oracle Content and Experience, enterprise users have access to all the features that standard users have access to, plus:
  • Create, manage, view, publish, and interact with content items, digital assets, and collections.
Any users that need to actually use Oracle Content and Experience must be assigned the standard user or enterprise user role. These roles aren’t assigned by default to any user.

See Task and Feature Comparison by Application Role.

Visitor (CECSitesVisitor) Access sites restricted to visitors. This role applies if a site is set to be accessed only by visitors. If that restriction is enabled, only users with this role will be able to access the site. See Change Site Security in Creating Experiences with Oracle Content and Experience.

Visitors don’t require a license.

Integration user (CECIntegrationUser) Used to impersonate another user while performing operations through the Social REST endpoints of the REST API for Collaboration. Create a dedicated “Integration User” and assign it the integration user role. Make sure no one deletes the integration user you create. If this user is deleted, operations performed through the Social REST endpoints of the REST API for Collaboration won't work correctly.

Note: This role is for an internal user, not an actual person. Users assigned this role can’t use the Oracle Content and Experience user interface.

See “Social Resource” in REST API for Collaboration.

External user (CECExternalUser) Reserved for future use. Do not use this role. Users assigned this role can’t use the Oracle Content and Experience user interface.