Are multiple migration engineers sharing a single BitTitan login because role-based access has not been configured for the team?

BitTitan supports role-based access control through MSPComplete, letting you add additional users under your BitTitan account with defined permission scopes. This makes it possible to give engineers access only to the customer projects they need, without granting full account admin rights.

BitTitan supports several access levels: account admin can manage billing, licensing, and all projects; project manager can create and manage projects within assigned customers; and migration engineer can run migration jobs within assigned projects but cannot change project configuration or purchase licenses.

On a 10-engineer team working across two acquisition migration projects, creating individual BitTitan user accounts with project-scoped access ensures each engineer has a unique login, every portal action is tied to a specific user, and credential sharing is removed from the workflow.

When credentials are shared, accountability disappears as well. If someone unintentionally changes a project setting, there is no audit trail showing who made the change. Assigning individual accounts brings that traceability back.

Have you provisioned individual BitTitan user accounts for each engineer on your migration team with appropriate role-based access?

#BitTitan #MigrationWiz