RBAC Clarity & Access Control Confidence Assessment

Welcome to the RBAC Clarity & Access Control Confidence Assessment. This survey explores your experience configuring and managing roles, permissions, and access controls in this product. It should take approximately 5–7 minutes. Your participation is entirely voluntary and you may stop at any time. There are no right or wrong answers—we are interested in your honest experience. All responses are confidential, anonymized, and will be reported only in aggregate to improve the product.

Which of the following best describes your primary admin role for this product?

• Organization/tenant admin
• Workspace/project admin
• Team/group admin
• Security/compliance admin
• Support/helpdesk admin
• I'm the only admin

The next few questions present common admin scenarios. Please select the outcome you would expect based on your current understanding.

How clear are the role names and labels used in this product?

Think of a recent time (within the last 90 days) when a role or permission change did not produce the outcome you expected. Please describe what happened.

What is your primary region?

• Africa
• Asia
• Europe
• North America
• Oceania
• South America
• Prefer not to say

Thank you for your time. Your feedback will directly inform improvements to roles, permissions, and access control in this product.

How long have you been an admin for this product?

• Less than 1 month
• 1–3 months
• 3–6 months
• 6–12 months
• 1–2 years
• More than 2 years

Scenario: You grant a mid-level role (e.g., Editor) at a specific project level. What outcome do you expect?

• Can create/edit content only within that project
• Can create/edit content across all projects
• Can view across the organization but edit nowhere
• Cannot access until explicitly added
• Not sure

How clear are the permission descriptions in this product?

Based on your responses in this survey, what is the single most important improvement that would make roles and permissions clearer or more predictable?

Approximately how many employees are in your organization?

• 1–10
• 11–50
• 51–200
• 201–1,000
• 1,001–5,000
• 5,001–10,000
• 10,001+
• Prefer not to say

Approximately how many active user accounts do you manage in this product?

• 1–10
• 11–50
• 51–200
• 201–500
• 501–1,000
• 1,001–5,000
• 5,001+

Scenario: You assign a high-level role at the organization level. What should happen to nested resources (workspaces/projects)?

• Applies to all nested resources by default
• Applies to nested resources, but can be overridden
• Does not apply to nested resources
• Not sure

How clear is the scope and inheritance model (e.g., organization → workspace → project) in this product?

Which industry best describes your organization?

• Technology
• Education
• Healthcare
• Finance
• Government
• Nonprofit
• Retail/Consumer
• Manufacturing
• Other
• Prefer not to say

Which environments do you primarily administer?

• Production only
• Non-production only (e.g., sandbox/staging)
• Both equally
• Not sure

Before saving role or permission changes, which one check do you most often perform?

• Review a preview/impact summary
• Use a test user or impersonation
• Apply in staging/sandbox first
• Ask a colleague to verify
• Proceed and monitor audit logs
• I do not perform any checks
• Other (please specify)

In the last 30 days, how often did role or permission changes behave as you expected?

After configuring roles and permissions, how confident are you that access levels are set correctly?

How satisfied are you with the in-product guidance and documentation about roles and permissions?

Please rank the following areas from most confusing (top) to least confusing (bottom) based on your experience.

1. Role names
2. Permission descriptions
3. Scopes/levels (org/workspace/project)
4. Default access for new members
5. Group/team behavior
6. Inheritance and overrides