How can we help?

Suspected unauthorized access should be treated as a potential security incident. Examples include unexpected account activity, unfamiliar changes to workspace settings, unrecognized actions, or evidence that your credentials may have been exposed. The appropriate response depends on whether the account is still accessible and whether business information may be affected. What are possible warning signs? 1. Unexpected changes to your account information. 2. Unrecognized workspace activity. 3. Changes to user roles or permissions that you did not authorize. 4. Unexpected integration activity. 5. Unfamiliar business operations. 6. Security-related messages you did not initiate. 7. Evidence that your password has been exposed. 8. Suspicious activity associated with your registered email account. What should I do immediately? Step 1: Secure your credentials. If you can still access the account, use the supported password change or recovery process to replace any potentially compromised password. Step 2: Secure your email account. Your registered email address may be important for account recovery. Step 3: Notify the appropriate administrator. If the affected account belongs to an Enterprise workspace, inform the organization's security or administrative contact. Step 4: Review relevant activity. Where available and authorized, examine recent operational records and unexpected changes. Step 5: Review external integrations. Determine whether connected applications or credentials may also be affected. Step 6: Follow incident response procedures. If your organization has an established security process, use it. Step 7: Contact Polyosync Support. Provide a clear description of the suspected incident. What if I can no longer sign in? Use the supported account recovery process. If recovery is unavailable or the account appears to have been taken over, contact Support and the relevant organization administrator. What information is useful for an investigation? 1. The affected account email address. 2. The relevant workspace. 3. Approximate date and time. 4. Description of suspicious activity. 5. Relevant error messages. 6. Non-sensitive screenshots. 7. Any known external systems involved. Do not send passwords, API keys, or authentication tokens. Can audit logs help? Where the relevant audit information is available, it may support an investigation. However, audit records should not be assumed to capture every event. What if the incident involves a connected CRM or other service? Follow the external provider's security procedures as well. Securing the Polyosync account alone may not address every affected system. Recommended practice Act promptly, secure affected credentials, notify responsible administrators, and investigate the incident using available operational evidence.