Difference between Public role and No Role

[miyu]

I do not know the difference between Public role and no role.
What is the difference between the two roles?

[Jaspal Singh]

Hi Miyu,

Public - Anyone can see it even if they don't have a ServiceNow login

No Role - Needs to authenticate to ServiceNow to access

[vkachineni]

What does the "Guest" account have?

[Harish KM]

Hi ,

Public role : You dont need access to login in to the servicenow instance. Without logging in a User can view anything for example surveys or KB article. But to do this the applications needs to have public role as well.

No role  means they have to authenticate to Service Now in order to view anything

[Riya Verma]

Hi @miyu ,

Hope you are doing great.

The main difference between the two is in the level of access they provide.

1. Public Role: When a user is assigned the "Public" role, it means they have some level of access to the system, even if they don't have any specific roles assigned. The "Public" role typically grants basic, limited access to certain features or data, such as the ability to log in and perform very basic actions. It's a way to provide minimal access to all users.

2. No Role: When a user has "No Role" assigned, it means they have no predefined access rights or permissions within the system. They essentially have no role-based access. This might be appropriate for users who should not have any access to the system until specific roles are assigned to them.

In short, "Public" role provides minimal default access, while "No Role" means the user has no predefined access and will need roles assigned to access any part of the system.