How can an administrator grant, update, or revoke employee access in Polyosync?
Managing employee access is an important part of keeping a Polyosync business environment secure.
Organizations should provide access only to people who need it and adjust permissions when their responsibilities change.
Who can manage access?
Access management operations depend on the permissions associated with the relevant administrative role.
Not every authenticated employee is authorized to invite users or change permissions.
How can an employee receive access?
1. An authorized administrator identifies the relevant business environment.
2. The administrator determines the employee's responsibilities.
3. The administrator uses the supported employee invitation or access management functionality.
4. The appropriate role is selected.
5. The employee completes the required invitation or account access process.
6. The administrator verifies that the employee has the intended access.
The exact interface steps may differ depending on the account configuration.
How should existing permissions be changed?
When an employee's responsibilities change, an authorized administrator should review their current access.
The administrator can then use the available management controls to make supported changes.
After updating permissions, verify that the employee can access the necessary functionality and no longer has unnecessary privileges.
When should access be revoked?
Access should be reviewed when:
1. An employee leaves the organization.
2. A contractor's engagement ends.
3. An employee changes departments.
4. A temporary assignment is completed.
5. A user no longer requires a particular resource.
6. A security incident requires access restrictions.
Does removing access automatically delete the employee's historical actions?
Not necessarily.
Membership management and retention of operational or audit records are separate concerns.
Historical information may remain subject to applicable retention and legal requirements.
What about integrations configured by a departing employee?
Review whether any external connections depend on that employee's credentials or account.
Those integrations may require reauthorization or another supported administrative action.
What about AI Employees created by that user?
Review the ownership, configuration, and operational dependencies of relevant AI Employees.
Do not assume that removing a human user automatically deletes or disables every related resource.
Recommended practice
Maintain an employee access lifecycle covering onboarding, role changes, periodic reviews, and offboarding.