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.
Information
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.
You can copy the settings of the selected role to create a new role. Press [Copy Role to Create New] to navigate to the new role creation screen, where the settings of the selected role will be reflected in their initial state. Please make any necessary edits and create the role.
You can deselect all or grant all for each permission item. When individual permissions are added, a [Deselect All / Grant All] button will be provided for each individual permission.
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.
All Members
Information about all members can be read.
Members with this role assigned Information about members assigned the same role can be read.
This mainly affects viewing the API key list screen, detail screen, and reading the API key during API preview. Information about all API keys will be accessible for reading.
You can view the list of duplicated environments and access each environment.
Caution
The created environment can be accessed even without read permissions if the URL of the duplicated environment is known. This behavior may change in future updates.
When creating an environment, having creation permissions allows you to verify a lot of data, as it enables you to copy the settings and content from the production environment.
Only reviews created by members of this role You can only view reviews requested by members assigned the same role. The determination of whether they belong to the same role uses the current role, not the role at the time of the review request.
In addition to the operations possible with "Edit/Comment only," you can approve the review to publish content, approve the review to end content publication, and delete comments (including comments from AI reviews).
Edit/Comment Only
You can end, resubmit, post comments, edit review titles and descriptions, set scheduled times, configure reviewers, assign AI reviewers on the review screen (manual execution), and execute re-reviews.
Edit (None)
You cannot edit anything regarding the review.
Information
Permissions for Executing AI Reviews 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 the target content includes any data, 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 automatic execution will be performed by the system, and can be executed regardless of the operator's permissions.
This mainly affects viewing the media list screen, reading images from the rich editor, and reading in image/file fields.
All Media
Information about all media (images and files) can be read.
Media Created by Members of This Role Only
You can only view media created by members assigned the same role. The determination of whether they belong to the same role uses the current role, not the role at the time of media creation.
This mainly affects viewing the content list screen and detail screen, as well as reading content reference fields.
All Content
You can view all content.
Content Created by Members of This Role Only
You can only view content created by members assigned the same role. The determination of whether they belong to the same role uses the current role, not the role at the time of content creation.
You can hide developer settings. If set to hidden, the following menus will be hidden.
Custom Fields
API Settings
API Preview
▼View When Developer Settings Are Set to "Visible"
▼View When Developer Settings Are Set to "Hidden"
Caution
You can view the Custom Field 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 a default role that has permissions to perform all operations. This role cannot be edited (permissions cannot be changed) or deleted. Additionally, it must be assigned to at least one person within the service.
There are operations in the management screen that can only be executed by the administrator role. Therefore, when comparing a newly created role with all permissions granted to the administrator role, the administrator role can perform a wider range of operations.
Operations that can only be executed by the administrator role include the following:
Viewing and operating certain items in service settings
Creating, editing, and deleting API keys
Changing environment names and label colors
Creating, editing, and deleting API groups
Granting and editing roles other than the role to which one belongs
Default permissions are permissions applied at the service level, and restrictions are applied to all APIs / content. This is effective when you want to set permissions for the entire service at once.
On the other hand, individual permissions are permissions applied at the API level, which can override default permissions. With individual permissions, you can set the following items:
Members with roles other than the administrator role are only permitted to perform the following actions regarding role granting and editing.
Edit the permissions of the role they belong to
Grant or revoke their own role to/from another member
If you hold a role other than the administrator role and wish to grant or edit roles other than your own, please grant the relevant role to the member in question. Multiple roles can be assigned to a member, and stronger permissions take precedence.
Assume there are two roles: "Site A Administrator" and "Site A Operator," and there is a member with the "Site A Administrator" role.
Now, consider the case where this member wants to add a member who holds the "Site A Operator" role (a role they do not possess). In this case, by granting the "Site A Operator" role to this member, they will be able to select the "Site A Operator" role when adding a member.
▼ When adding a member, the "Site A Operator" role will also become selectable
Information
Caution
