What is the default number of roles for Partner Community or Customer Community Plus user licenses?

What is the default number of roles for Partner Community or Customer Community Plus user licenses?

• A. Two roles
• B. One role
• C. Three roles
• D. Four roles

Answer: (B)

The default number of roles for Partner Community or Customer Community Plus user licenses is one role. This configuration aligns with the streamlined access and management of users in the Community Cloud, where each user is typically assigned to a single role. This structure allows for clear permission sets and simplifies reporting and analytics related to user activities within the community. Having a single role for such user licenses ensures that all community members have a defined identity within the system, which aids in role-based access controls and enhances the overall user experience. By limiting the number of roles, the system reduces complexity for administrators who need to manage user permissions and provides a straightforward way to assign responsibilities across the community. This arrangement supports the principle of least privilege, allowing users to access only the information and functionality necessary for their roles. The additional options suggesting multiple roles do not reflect the design philosophy intended for these specific user licenses, which prioritize simplicity and clarity in user management.

The default number of roles for Partner Community or Customer Community Plus user licenses is one role. This configuration aligns with the streamlined access and management of users in the Community Cloud, where each user is typically assigned to a single role. This structure allows for clear permission sets and simplifies reporting and analytics related to user activities within the community.

Having a single role for such user licenses ensures that all community members have a defined identity within the system, which aids in role-based access controls and enhances the overall user experience. By limiting the number of roles, the system reduces complexity for administrators who need to manage user permissions and provides a straightforward way to assign responsibilities across the community. This arrangement supports the principle of least privilege, allowing users to access only the information and functionality necessary for their roles.

The additional options suggesting multiple roles do not reflect the design philosophy intended for these specific user licenses, which prioritize simplicity and clarity in user management.