Step 2 – Website permissions

You should have already set up your permissions model using RBAC, so when you first look at the website-specific permissions, it will carry through the permissions set for the role groups, for example Account administrators likely have full access to this website due to account-level role permissions. You can set specific permissions for each group and user, giving you granularity for whether a role needs access to the whole site, or just a section.

The 4 access options

Can see

This allows the designated role groups or users to view the report only. Without this permission, the site will not be displayed in the overview, and direct links to this report (unless a share link) will not work.

Can contribute

This allows the selected role groups or users to make decisions inside the report, like learning an unrecognized spelling or ignoring a broken link. Choosing “can contribute” will enable “can see” by default. This setting does not allow users to retest.

Can test

This allows the selected role groups or users to test on demand, whether it is the whole report or just a single page. Choosing “can test” will enable “can see” by default, but is unconnected to “can contribute.”

Can admin

This allows the selected role groups or users to act as administrators for this site or section report. Giving users the “can admin” permission will allow them to add other more restricted access users to the site and give them permissions for viewing, testing, or contributing to the report. “Can admin” will enable the other three access options by default.

Let’s go back to Adding a website overview or move on to Step 3 – What we test.

Need extra help?

Chat with our support team now and we'll be happy to help you with any issues