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, as well as perform the following various operations.
You can filter by role name.
Press the [Add] button to navigate to the new role creation screen.
Additionally, the menu that appears when you press the three-dot menu for each role is as follows.
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.
This will delete the selected role.
This is the screen for creating a new role.
Once you have completed the necessary settings, press [Create] to 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.
For individual permissions, please refer to the section on "Default Permissions and Individual Permissions" below.
This is the screen for editing the created roles.
You can copy the selected role and create a new role.
This behaves the same as when you press [Copy and Create New] on the role list screen.
This will delete the currently opened role.
This will reflect the changes in 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 the duplicated environment.
You can view all review requests.
Only reviews created by members of this role
You can only view reviews requested by members assigned the same role.
The determination of whether members belong to the same role is based on the current role, not the role at the time of the review request.
You can only view reviews that you have requested.
You cannot view any reviews.
You can submit a review request.
In addition to the operations possible with "Edit/Comment only," you can approve the review and delete comments (including comments from AI Review).
With the "Approve + Edit/Comment" permission, you can approve reviews, but you cannot publish, schedule for publication, end publication, or schedule to end publication at the time of approval.
To change the publication status, the following permissions are additionally required for the target content.
You can complete, reapply, post comments, edit the review title and description, set the scheduled time, configure the reviewer, assign the AI Reviewer on the review screen (manual execution), and execute a re-review.
No edits can be made regarding the review.
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 mainly affects viewing the media list screen, reading images from the Rich Text Editor, and reading in image/file fields.
You will be able to read information about all media (images and files).
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.
You can only view media that you have uploaded.
You cannot view any media.
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.
This mainly affects reading the API list displayed in the sidebar and reading content reference fields.
You can view information about all APIs.
You will be able to create APIs.
You will be able to configure API settings, set custom fields, and rearrange or move APIs between groups.
You will be able to delete APIs.
This mainly affects viewing the content list screen and detail screen, as well as reading content reference fields.
You can view all content.
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 only view content that you have created.
You cannot view any content.
You can save new content as a draft.
You can publish new content.
[Operations Not Affecting Published Content]
You can save content that is "Draft" or "Published and Draft" as a draft.
You can discard the draft of content that is "Published and Draft".
You can revert "Published Ended" content to draft.
You can change the content ID of content that is "Draft" or "Published Ended".
You can rearrange content that is "Draft" or "Published Ended".
You can change the publish date of content that is "Draft" or "Published Ended".
Change Content Creator
You can change the content creator.
You can change the draftKey of content that is "Draft" or "Published and Draft".
[Operations Affecting Published Content]
You can publish or schedule publication of unapproved content that is "Draft" or "Published and Draft".
You can publish or schedule publication of approved content that is "Draft" or "Published and Draft".
You can end publication or schedule end publication of unapproved content that is "Published" or "Published and Draft".
You can end publication or schedule end publication of approved content that is "Published" or "Published and Draft".
You can revert "Published" content to draft.
You can change the content ID of content that is "Published" or "Published and Draft".
You can rearrange content that is "Published" or "Published and Draft".
You can change the publish date of content that is "Published" or "Published and Draft".
You can delete content.
You can hide developer settings. If set to hidden, the following menus will not be displayed.
▼View When Developer Settings are Set to "Visible"
▼View When Developer Settings are Set to "Hidden"
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 a default role that has permissions for all operations.
This role cannot edit (change permission contents) or delete.
Additionally, it must be assigned to at least one member within the Service.
There are operations in the Administration console 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:
Default permissions are permissions applied at the service level, and restrictions are applied to all APIs / contents.
This is effective when you want to set permissions for the entire service at once.
On the other hand, custom permissions are permissions applied at the API level, which can override default permissions.
With custom permissions, you can set 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, the determination will be API creation permission granted.
Members with roles other than the Administrator role are only permitted to perform the following actions regarding role assignment and editing.
If you hold a role other than the Administrator role and wish to grant or edit roles other than your own, please assign the relevant role to the corresponding member. Roles can be assigned to multiple members, 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 with 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 be selectable
