Understanding Projects and Teams

3.1 Understanding Projects and Teams

In ACTIONBRIDGE, work is organized around Projects. Each project serves as a workspace for tasks, members, workflows, and Teams integration — offering a focused and collaborative environment.

What is a Project?

  • A Project represents a unit of work such as a product, department, client, or initiative.
  • Projects inherit tenant-level (organizational) settings like SSO and licensing, but manage their own members, roles, and workflows independently.
  • Each user must be explicitly added to a project to access its tasks and content.
  • Projects support task lists, comments, subtasks, dependencies, Gantt views, and reporting — all scoped within the project.

Teams Integration (One Channel per Project)

  • Each project can be linked to one Microsoft Teams channel tab at a time.
  • To link a project to a Teams channel, open the tab and follow the project selection process.
  • If the project is already linked to another channel, you must first unlink it before reassigning.
  • This ensures one-to-one clarity between Teams channels and ACTIONBRIDGE projects.

Managing Project Members

  • Members can be added individually to each project by project admins.
  • Roles include Admin, Editor, and Viewer, each with different permissions.
  • Only licensed users from the same Microsoft 365 tenant can be added.

Tips

  • Use separate projects to isolate client work, product areas, or internal teams.
  • If you want to change a project’s linked Teams tab, make sure to unlink the existing one first.
  • Admins can manage access and roles from the project’s settings page.

With clearly scoped projects and structured Teams integration, ACTIONBRIDGE helps you keep collaboration clean, access secure, and workflows aligned across your organization.

2025-07-07
ACTIONBRIDGE projects
Microsoft Teams integration
one channel per project
project members
project roles
tenant inheritance
project workspace
unlink project channel
manage team access
project setup

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.