Can multiple employees share one Polyosync login, and how should team access be managed?
Employees should use individual Polyosync accounts rather than sharing a single set of login credentials.
Individual identities support appropriate access control, operational accountability, and more effective security management.
Enterprise organizations can invite employees and assign roles according to their responsibilities.
Why should accounts not be shared?
Shared credentials create several security problems.
1. It becomes difficult to determine who performed an action.
2. Access cannot be managed independently for each employee.
3. A compromised password may affect multiple people.
4. Removing one employee's access becomes more complicated.
5. Administrative responsibility becomes unclear.
6. Security investigations may lack reliable attribution.
7. Employees may receive more permissions than necessary.
How should a new employee receive access?
Step 1: Identify the workspace they need.
Step 2: Determine their responsibilities.
Step 3: Use the supported team invitation functionality.
Step 4: Enter the employee's account information.
Step 5: Select the appropriate role.
Step 6: Complete the invitation process.
Step 7: Verify that the employee can access the intended functionality.
Step 8: Review access after the employee's responsibilities change.
Which Enterprise roles are available?
The Enterprise team management interface includes:
1. Member.
2. Manager.
3. AI Admin.
4. Security Admin.
5. Admin.
6. Viewer.
The exact permissions associated with each role depend on the implemented authorization rules.
Should managers automatically receive administrator access?
No.
Permissions should reflect actual operational requirements rather than job title alone.
What should happen when an employee leaves?
An authorized administrator should review and revoke access as appropriate.
Any related external integrations or operational dependencies should also be examined.
Can an employee access several workspaces?
Access depends on the supported membership configuration and the permissions granted for the relevant environments.
Organization membership does not automatically imply unrestricted access to every workspace.
What if two employees need to perform the same tasks?
They should receive appropriate individual permissions.
Sharing responsibilities does not require sharing credentials.
Recommended practice
Use individual accounts, assign roles deliberately, and review access throughout the employee lifecycle.