Custom access and how to transition to roles

この記事では、Confluence の新しいロールベースのアクセス モデルについて説明します。これには、ロールのベータ版への参加にサインアップした既存のサイトと、新しいロール専用サイトの両方が含まれます。

When roles are enabled in your Confluence instance, go to Confluence settings Security, then select Space permissions, then Manage roles or go to the Users page in Space settings.

ご使用の環境で確認できない場合は、インスタンスでロールがまだ有効になっていません。

 

To make managing space access easier and more predictable, Confluence is transitioning its model from assigning individual granular permissions (which can have endless combinations) to assigning preset roles.

What’s the difference between “Custom access” and custom roles?

To help you plan for this transition, Confluence will temporarily support both models. This allows us to make roles available to you without changing anyone’s access and means that no user will have more or fewer permissions than they had before.

If a user, group, or user class is currently on the old model, they’ll display as having “Custom access”. If they’re on the new model, the Manage access screen will display their role.

“Custom access” doesn’t mean “Custom role”. “Custom access” means no role has been assigned yet.

A comparison of a Confluence user group with the manager role and one with custom access.

Recommendations for when to use “Custom access”

In general, we recommend against using custom access because eventually, all custom access accounts will have to switch to a role. Instead, we recommend moving over to roles as soon as possible to keep your overall transition to roles more manageable.

We understand Confluence’s default roles won’t cover all access cases your organization may need, so some customization will be needed. If so, we recommend creating custom roles to satisfy your customization needs.

That said, it may take you some time to identify the best custom roles to create for your organization and to effectively assign them throughout your Confluence instance. While you’re creating and assigning custom roles, custom access is useful to prevent any disruptions to Confluence users.

But remember, each custom access configuration you add may create more transition debt.

How to transition to roles

First, any user or group with a permissions configuration that exactly matches a role will automatically be assigned that role as soon as the role experience lands on your site. Otherwise, they will display with “Custom access”.

Transition individual users and groups to roles

To switch a user or group with custom access to a role, simply open the role dropdown and choose one of the following options:

  • 管理

  • マネージャー

  • 協力者

  • Viewer

To review what permissions are included in each role:

  1. Open the (more actions) menu and select Manage access.

  2. Open the role dropdown on the left.

  3. As you select any of the roles, the permissions will update to reflect what permissions that role includes but no change will be saved. This way, you can review the permissions before committing to them.

  4. If you want to commit to a role, select Save.

  5. Select Cancel to leave the permissions the way they were.

Transition to roles in bulk

To assign a role to a user or group in all spaces:

  1. In product settings, go to Space permissions.

  2. In the All spaces tab, select Make a bulk access change.

  3. Indicate a user, group, or user class.

  4. Select Add or change access.

  5. Select which spaces: All (excluding personal), All, or Only personal.

  6. Choose a role.

  7. Select Add to all.

What role should you choose?

In general, choose:

  • Viewer if you don’t want them to edit anything

  • Collaborator if you want them to edit content but not much more

  • Manager if you want them to manage content and access but not big space actions like deleting the space or allowing anonymous access

  • Admin if you want them to control everything in the space

さらにヘルプが必要ですか?

アトラシアン コミュニティをご利用ください。