1. Home
  2. Help Center
  3. Team Management
  4. Understanding Scopes

Understanding Scopes

What are Scopes?

Scopes define what areas and features a team member can access within your organization. While roles determine what actions a user can perform (view, edit, admin), scopes determine which parts of the organization they can access.

How Scopes Work

Scopes control access to different functional areas of your AppGram organization. When you assign a scope to a team member, you're defining which sections of the dashboard and which types of data they can interact with.

Available Scopes

  • Feedback: Access to wishlist items, feature requests, and user feedback
  • Roadmap: Access to roadmap planning and status updates
  • Changelog: Access to release notes and product updates
  • Support: Access to support tickets and customer conversations
  • Forms: Access to forms and form submissions
  • Surveys: Access to surveys and survey responses
  • Help Center: Access to help articles and documentation
  • Status Page: Access to status page and incident management
  • Analytics: Access to reports and insights

Assigning Scopes

When inviting a team member or editing their permissions:

  1. Go to Organization Settings → Team
  2. Click on the team member or invite a new one
  3. Under Scope, select which areas they should have access to
  4. Save your changes

Scope + Role Interaction

Scopes work together with roles to provide granular access control:

Example Role Scope Result
Full Admin Admin All Scopes Can manage everything across the organization
Product Manager Editor Feedback, Roadmap, Changelog Can edit product-related content only
Support Agent Editor Support, Help Center Can handle support tickets and manage help docs
Marketing Editor Changelog, Status Page Can publish updates and manage communications
Stakeholder Viewer Roadmap, Analytics Can view progress and reports, cannot modify

What Team Members See

When a team member logs into AppGram, they will only see:

  • Sidebar items for their assigned scopes
  • Data and content within those scopes
  • Actions permitted by their role within those scopes

Areas outside their scope are hidden from their dashboard entirely.

Best Practices

  • Match scopes to job function: Give team members access to the areas relevant to their work
  • Start narrow, expand as needed: Begin with minimal scopes and add more if necessary
  • Review regularly: Audit scopes when team members change roles
  • Use for compliance: Scopes help maintain data segregation for regulatory requirements