Polyosync Help Center

How can we help?

Browse help articles or contact our support team.

Request Support

How should administrators protect privileged Polyosync accounts?

Privileged accounts require particular attention because they may be authorized to perform important administrative or security-related operations. Enterprise administrators should protect their accounts and avoid unnecessary use of elevated permissions. Polyosync Enterprise includes Admin, Security Admin, and AI Admin role options. The exact permissions available to these roles depend on the implemented authorization model. Why are privileged accounts important? An account with elevated permissions may be able to affect important configuration, team access, AI operations, or other protected functionality. Unauthorized access to such an account can therefore create greater operational risk than compromise of a narrowly scoped account. Recommended security measures 1. Use a unique, strong password where password authentication is applicable. 2. Protect the associated email account. 3. Avoid sharing credentials. 4. Use a trusted device. 5. Keep the device operating system and browser updated. 6. Lock the device when unattended. 7. Sign out on shared or untrusted devices. 8. Avoid granting elevated permissions unnecessarily. 9. Review administrative role assignments regularly. 10. Follow the organization's security procedures. 11. Review unexpected administrative activity. 12. Report suspected compromise promptly. Should every administrator have unrestricted access? No. Administrative responsibilities should be assigned according to operational requirements and the available role structure. An administrator's role should not be treated as authorization to bypass all platform security controls. What is separation of duties? Separation of duties is a governance practice that distributes sensitive responsibilities among appropriate people. For example, an organization may distinguish AI workforce administration from security oversight. The appropriate arrangement depends on the organization's size, internal policies, and available permissions. Should privileged accounts be used for ordinary tasks? Where practical, organizations should minimize unnecessary use of elevated privileges. The specific approach depends on the supported account and role management functionality. What should happen if an administrator leaves? Review and revoke their access promptly through the supported management process. Reassign important responsibilities and examine integrations or operational dependencies associated with the departing administrator. What if a privileged account is compromised? Follow the organization's incident response process. Secure credentials, investigate relevant activity, review affected systems, and contact Polyosync Support where necessary. Recommended practice Protect privileged accounts through strong authentication hygiene, carefully assigned permissions, and regular administrative access reviews.