Role-Based Access Control

3.3 Role-Based Access Control

ACTIONBRIDGE uses a clear and flexible role-based access control (RBAC) model at the project level. Roles determine what users can see and do within each project — from task editing to member management.

Available Roles

  • Admin: Full access to all project features, including:
    • Managing project settings and linked Teams tab
    • Adding/removing members and changing their roles
    • Creating, editing, deleting tasks
    • Configuring workflows, priorities, and integrations
  • Editor (default role): Focused on execution. Can:
    • Create and edit tasks
    • Comment and mention team members
    • Change task status, priority, and assignments
    • View task activity and deadlines
  • Viewer: Read-only access. Can:
    • View tasks and comments
    • Track progress and read change logs

Default Role Assignment

  • When a user joins a project (e.g. via Microsoft Teams tab), they are assigned the Editor role by default.
  • Project admins can later upgrade or downgrade the role as needed.

Assigning and Changing Roles

  • Only project admins can assign or change roles in the Members tab of Project Settings.
  • Changes take effect immediately and are scoped to the current project only.

Best Practices

  • Keep at least two Admins per project for redundancy and safety.
  • Use the Viewer role for external reviewers, clients, or stakeholders.
  • Audit roles regularly to maintain appropriate access control.

With project-scoped roles and default permissions that match user intent, ACTIONBRIDGE supports effective teamwork while keeping control, visibility, and responsibility clear.

2025-07-07
ACTIONBRIDGE roles
project permissions
role-based access
admin editor viewer
default editor role
manage project members
user roles
access control
Teams project roles
RBAC

Sho Shimoda

Spending more time creating help content than writing code — but only because making things easier is part of the product. Sho bridges engineering with user success, ensuring that every feature is not only powerful but also understandable. With a background in software development, AI integration, and product design, he now focuses on crafting systems where users don’t need to ask for help — but find it when they do.

Category

Tags

Search History

Authors

Sho Shimoda

Spending more time creating help content than writing code — but only because making things easier is part of the product. Sho bridges engineering with user success, ensuring that every feature is not only powerful but also understandable. With a background in software development, AI integration, and product design, he now focuses on crafting systems where users don’t need to ask for help — but find it when they do.

Koki Nin

Managing code, chasing after enhancements — and sometimes chasing bugs that turned out to be features. Koki is at the heart of the product’s technical evolution, turning feedback into fixes, and specs into shippable reality. He thrives where architecture meets iteration, always pushing for cleaner code and smoother experiences.

Yasushi Motoki

Helping users start strong with ACTIONBRIDGE. Yasushi leads the onboarding experience, translating product complexity into clarity. Whether guiding first-time users or supporting enterprise rollouts, he ensures every team gets value from day one — and knows exactly where to go next.