We ship continuously and publish meaningful changes in the changelog so operations teams can track what is new before enabling workflows.

No. Public route contracts are kept stable, and backward-compatible redirects are maintained for legacy marketing paths.

Major payroll and compliance updates are documented in changelog notes and related docs pages, including rollout caveats when needed.

Yes. Teams can validate in staging/demo flows and then promote to production once operational owners sign off.

Use the changelog tab plus product docs to review recently shipped capabilities, fixes, and workflow enhancements.

Access is role-based, sensitive actions are logged, and user-facing flows are designed to avoid exposing protected data across roles.

Yes. Permissions are scoped by role so employee views, manager controls, and client-facing flows only expose the required data.

Checkout and subscription flows are routed through Stripe integrations, and billing management is handled via secure portal links.

Yes. Key operations such as approvals, edits, and workflow transitions are retained for operational review and compliance traceability.

See the Privacy page for policy terms and contact support if your legal or compliance team needs additional clarification.

You can review the latest terms at any time from the Terms page in the footer and legal navigation links.

Plan management and cancellations are handled in billing settings through secure app routes and billing portal actions.

Core access starts in trial mode, then billing workflows and plan limits apply based on the selected subscription tier.

Yes. Domain and brand controls are available through website and marketing modules, with setup guidance available in docs.

Support scope depends on your plan and use case. Contact options are listed on the support and contact pages for rollout teams.