'Explicit Roles' plugin installation throws 403-forbidden error in Agent WorkspaceIssue 'Explicit Roles' plugin installation throws 403-forbidden error in Agent WorkspaceCause 'Explicit Roles' plugin installation throws 403-forbidden error in Agent Workspace (which can be seen in browser console, network tab), which is why this issue is occurring and this is working as expected. This is happening because of a dependent plugin that gets activated called 'Explicit Roles' plugin. Which makes it so that every user in the system must have a role in order to have access to the system. Once the plugin is activated, it introduces a new snc_internal role and adjusts ACLs (access control list) to use that role which includes REST API access rights which is what the graphQL calls probably lose access temporarily. This is also reproducible in Agent Workspace.ResolutionWhen activating the explicit roles plugin, users are required to logout and log back in to get the snc_internal role assigned to them. Dynamically assigning roles to users is not supported. This is working as expected.