Protect your Rooket account and every connected publishing destination.
Use individual accounts
Each teammate should use their own login. Do not share passwords. Remove access when a teammate no longer needs the workspace.
Protect publishing connections
Use provider authorization flows and OAuth whenever available. Review the connected account, site, page, or channel before enabling publishing.
Keep secrets out of support messages
Rooket support will never ask for your normal provider password or a copied OAuth token. Do not send passwords, API secrets, access tokens, recovery codes, encryption keys, or payment-card details.
Respond to suspected access issues
If you believe an account or connection was compromised, revoke access at the provider, disconnect the destination in Rooket, update the affected credentials, and contact support.
Control automated publishing
Use approval requirements and the automatic-publishing switch to match your risk tolerance. Pause publishing while investigating unexpected output or destination activity.
Share only necessary diagnostics
When requesting help, provide the workspace name, affected feature, item or job identifier, approximate time, and a description of the behavior. Remove secrets and unrelated personal information from screenshots.