Documentation hub
Find the guide for your next step.
Start with platform evaluation, client onboarding, migration or integration planning. Use the linked product and evidence pages to check the current scope before implementation.
Start, operate, troubleshoot, and recover
Public guide scope · exact availability follows the applicable release
Choose the task you need.
Source: Dayrook product requirements, operating runbooks, and route contracts5 matching tasks
Getting started
Set up the workspace, region, customer, identity, first agent, first ticket, protection policy, and report.
Review product scope
Explore each product’s operating model, evaluation questions and support boundaries. These product overviews do not replace release-specific operating procedures.
Secure and govern
Review identity, tenant and region scope, approval, secrets, signed execution, audit, incident, and evidence controls.
Build and migrate integrations
Use the declared route contract, scoped identity, strict schemas, retry budget, webhook verification, and recovery path.
Troubleshoot and recover
Start from visible state and safe identifiers; confirm scope, retryability, rollback, cleanup, and the proof required to close the issue.
First-time setup: review the evaluation sequence
Workspace to first verified result
- Create or enter the authorized workspace and select the client data region before customer data is created.
- Add the customer, users, roles, MFA, and the minimum module permissions needed for the first workflow.
- Deploy the supported agent or connect the provider through its purpose-bound authorization path.
- Open the resulting device, service, backup, network, or cloud record and confirm tenant, customer, owner, and current state.
- Complete one bounded action, then verify the result in the source record, audit timeline, and customer-facing evidence.
Questions, answered
Documentation hub: common questions
Where should a new administrator start?
Use the customer onboarding guide, then follow the first-value path from workspace and data region through the first customer, agent, ticket, backup, and report.
How do I find a module procedure?
Start with the module name and the outcome you need, then choose setup, daily operation, administration, troubleshooting, or recovery guidance.
What belongs in a support handoff?
Include the affected tenant and customer scope, workflow, visible state, request or route ID, time window, impact, checks completed, and safe evidence. Never include credentials.