The role feature allows you to flexibly set operation permissions for members in the management screen.
Please use it when multiple members from different positions are managing content simultaneously, or when you want to set operation permissions by department or store.
The role is a feature available in the Business and Enterprise plans.
For details on the features available in each plan, please refer to the pricing page.
On the role list screen, you can view the roles you have created and perform the following actions.

You can filter the list by role name.
Click the [Add] button to go to the screen for creating a new role.
The menu displayed when you click the three-dot menu for a role is as follows.
You can copy the settings of the selected role to create a new role.
Click [Copy Role and Create New] to go to the screen for creating a new role. The selected role's settings are applied by default. Edit them as needed, then create the role.
Deletes the selected role.
Use this screen to create a new role.

Once you have configured the required items, click [Create] to create the role.
You can clear or select all checkboxes for each permission item.
When you add a Custom Permission, a [Clear All / Grant All] button is provided for each Custom Permission.
For individual permissions, please refer to the section on "Default Permissions and Individual Permissions" below.
This screen lets you edit a role you created.

You can copy the selected role to create a new one.
This works the same way as clicking [Copy and Create New] on the role list screen.
Deletes the currently open role.
Applies the changes to the role settings.
This section explains the details of various permissions that can be set using the role feature.
This mainly affects the viewing of the member list screen and detail screen, as well as the reading of reviewer, creator, updater information, and members currently editing.
Information about all members can be read.
Members with this role assigned
Information about members assigned the same role can be read.
Information about specified members can be read.
Members cannot be viewed.
Members can be created.
When creating a member, it is necessary to specify a role, so read permissions for the role are also required.
Members other than the administrator role can only specify the roles they belong to.
If you want to specify a role for the member that is not one you belong to, please assign that role to yourself.
For specific methods, please refer to "How to grant or edit roles other than the ones you belong to".
You will be able to change the roles associated with members.
You will need read permissions for the role.
Members other than those with the administrator role can only change the roles they belong to.
If you want to change a role that you do not belong to, please assign that role to yourself.
For specific methods, please refer to "How to grant or edit roles other than the ones you belong to".
You will be able to delete members.
This mainly affects viewing the role list and role detail screens.
You will be able to read information about all roles.
You will be able to read information about the roles you belong to.
You will not be able to view roles.
You will be able to create roles.
You will be able to edit the permissions of roles.
Members other than the administrator role can only edit the permissions of the roles they belong to, even if they have editing rights.
If you want to edit the permissions of a role that you do not belong to, please assign that role to yourself.
For specific instructions, please refer to "How to assign or edit roles other than the ones you belong to".
Essentially, changing to the Hobby plan grants the authority to stop the service.
This mainly affects viewing the API Key list screen, detail screen, and reading the API Key during API Preview.
All information regarding API Keys will be accessible for reading.
You can access the data transfer amount screen and content count screen in Service Settings.
You can view the list of duplicate environments and access all environments.
The list of duplicate environments will not be displayed, but you can access them directly if you know the URL.
This setting is equivalent to the traditional read permission. If you want to restrict access to environments more strictly, it is recommended to set it to "None" or "Only specific environments."
If you are using SAML authentication, you cannot access the URL directly even if you know it.
Only the explicitly specified environments can be listed and accessed. Environments that are not specified cannot be accessed even if the URL is known.
Access to duplicate environments is not allowed. Access is also not permitted if the URL is specified directly.
You can create a duplicate environment.
When creating an environment, having creation permissions allows you to verify a lot of data, as it enables the copying of settings and content from the production environment.
You can delete duplicated environments.
You can view all Review Requests.
Only reviews created by members with this Role
You can view only reviews requested by members assigned the same Role.
The current Role is used to determine whether members belong to the same Role, not the Role they had when submitting the Review Request.
You can view only the reviews you requested.
You cannot view reviews.
You can submit Review Requests.
In addition to the "Edit" operations, you can approve reviews and delete comments.
With the “Approve and Edit” permission, you can approve Review Requests, but you cannot publish or unpublish approved Content (including scheduling these actions).
After approval, you need the following additional permissions for the Content to change its publication status:
Permissions for Executing AI Review
To manually execute (or re-review) an AI review, in addition to the review permissions mentioned above, you must have “read permissions for all content related to the review target”.
If there is any data within the target content, such as referenced content or image data, for which you do not have read permissions, you will not be able to manually execute (or re-review) the AI review.
※Note that if "Automatic Review" is set to ON in the review settings, the execution will be performed by the system, and it can be executed regardless of the operator's permissions.
This primarily affects viewing the media list screen, reading images from the Rich Text Editor, and reading in image/file fields.
Information about all media (images and files) can be read.
You can only view media created by members assigned the same role. The current role is used to determine if you belong to the same role, not the role at the time of media creation.
You can only view media that you have uploaded yourself.
You cannot view any media at all.
You will be able to upload media.
You will be able to re-upload media, change file names, and set tags.
You will be able to delete media.
You can check the media Webhook settings by setting the media read permission to anything other than "None."
To edit the media Webhook settings, you need to set the media read permission to anything other than "None" and have edit permissions.
Primarily affects viewing the API list displayed in the sidebar and reading Content Reference fields.
You can view information about all APIs.
You can create APIs.
You can edit API Settings and Custom Field settings, reorder APIs, and move them between groups.
You can delete APIs.
Primarily affects viewing the Contents list and detail screens, and reading Content Reference fields.
You can view all content.
You can view only content created by members assigned the same role.
The current role is used to determine whether members belong to the same role, not the role they had when the content was created.
You can view only content you created.
You cannot view any content.
You can save new content as a Draft.
You can publish new content.
[Actions that do not affect published content]
You can save content with the status “Draft” or “Published with a draft” as a Draft.
You can discard the Draft of content with the status “Published with a draft.”
You can return content with the status “Unpublished” to Draft.
You can change the Content ID of content with the status “Draft” or “Unpublished.”
You can reorder content with the status “Draft” or “Unpublished.”
You can change the publication date of content with the status “Draft” or “Unpublished.”
Change the content creator
You can change the content creator.
You can change the draftKey of content with the status “Draft” or “Published with a draft.”
[Actions that affect published content]
You can publish or schedule unapproved content with the status “Draft” or “Published with a draft.”
You can publish or schedule approved content with the status “Draft” or “Published with a draft.”
You can unpublish or schedule unpublishing of unapproved content with the status “Published” or “Published with a draft.”
You can unpublish or schedule unpublishing of approved content with the status “Published” or “Published with a draft.”
You can return content with the status “Published” to Draft.
You can change the Content ID of content with the status “Published” or “Published with a draft.”
You can reorder content with the status “Published” or “Published with a draft.”
You can change the publication date of content with the status “Published” or “Published with a draft.”
You can delete content.
You can hide developer settings. When hidden, the following menu items will also be hidden.
▼How developer settings appear when set to “Show”

▼How developer settings appear when set to “Hide”

You can view Custom Fields and API Settings by directly entering the URL. The Developer Menu is intended for basic control, so if you need to restrict actual access, please use the permission settings related to the API.
The Administrator role is available by default and grants permission to perform all operations.
This role cannot be edited (its permissions cannot be changed) or deleted.
At least one member of the Service must be assigned this role.

Some operations in the Administration console can only be performed by members with the Administrator role.
Therefore, the Administrator role allows a broader range of operations than a newly created role with all permissions granted.
Examples of operations available only to the Administrator role include:
Default permissions are applied at the Service level and restrictions apply to all APIs and Content.
They are useful when you want to configure permissions for the entire Service at once.
In contrast, Custom Permissions are applied at the API level and can override default permissions.
With Custom Permissions, you can configure the following items:

Multiple roles can be assigned to a single member.
The association of roles to a member can be done from the member detail screen.
If the multiple roles assigned have different permissions, the role with broader permissions takes precedence.
Role A: No API creation permission
Role B: API creation permission granted
If a user belongs to both roles as described above, the determination will be API creation permission granted.
Members with a role other than the Administrator role are only allowed to perform the following actions related to assigning and editing roles:
If you have a role other than the Administrator role and want to assign or edit a role you do not belong to, assign that role to the relevant member. Multiple roles can be assigned to a member, and the role with the higher level of permissions takes precedence.
Suppose there are two roles, “Site A Administrator” and “Site A Operator,” and a member has the “Site A Administrator” role.

Now, suppose this member wants to add a member with the “Site A Operator” role, which they do not have.
In this case, assigning the “Site A Operator” role to this member will allow them to select that role when adding a member.

▼ “Site A Operator” will also be available for selection when adding a member
