Skip to content
LatidoFlow
Open navigation
Create account

Workspace administration

Keep access, credentials, limits, and migration evidence in one workspace.

Workspace owners and administrators control integration credentials and team records. Every customer should understand the reveal-once secret boundary, plan limits, and what an import or export does not carry.

Prepare the account and workspace

  1. Register and verify the email address. Email/password registration and supported Google sign-in create the initial account and workspace.
  2. Review the defaults. A new account starts with a Free plan, a default project, a Production environment, and a status page that you can rename and configure.
  3. Set workspace name and timezone. The timezone controls schedule display, quiet hours, and weekday/weekend semantic baselines.
  4. Create the first monitor. Use a dedicated uptime or heartbeat flow; do not use the optional demo tour as evidence that an external integration is active.

Manage people and roles

Owner

Full workspace administration, including billing, integrations, team access, and operational changes.

Admin

Operational and configuration access, including integration and team management where policy permits.

Member

Day-to-day monitoring and incident access without owner-level administration.

Viewer

Read access to the workspace surfaces allowed by policy.

Invite member sends an expiring email invitation. The recipient must accept from that address, either by signing in or by creating an account for the invited email. Resend invalidates the previous link; revoke, expiry, and reuse stop acceptance.

Issue and rotate ingestion credentials

Issue

Open Workspace integration, choose a deployment-specific name, issue the token, and copy the plaintext once into the intended runtime secret store.

Observe

The onboarding checklist records credential issuance, successful definition sync, and the first accepted real runtime mutation as separate milestones.

Rotate without a gap

Begin rotation, deploy the replacement, wait until that replacement reports runtime evidence, then complete cutover. The previous credential stays valid until cutover.

Revoke immediately

Use Emergency revoke when a credential may be exposed. Requests with that token begin returning 401; issue and deploy a replacement separately.

Issue, rotation, cutover, and revocation retain actor, time, token identifier, and last-four evidence without storing or exporting plaintext.

Migrate from Healthchecks.io

  1. Export Management API v3 JSON from Healthchecks.io. Upload the file on Workspace integration → Open Healthchecks importer.
  2. Review the preview. Confirm names, schedules, grace values, supported cron or interval mappings, and any warnings before writing monitors.
  3. Apply atomically. Stable source mapping makes a repeated import idempotent. Existing unrelated monitors are not replaced.
  4. Move the ping endpoint once. Update the real workload to the new LatidoFlow heartbeat URL, then wait for fresh accepted evidence.
  5. Verify before cleanup. The import is not complete until each intended monitor receives a new real signal. Prior provider health is not copied as LatidoFlow evidence.
  6. Use rollback conservatively. Rollback refuses destructive removal when later customer changes or evidence make the imported resource unsafe to delete.

Export operational evidence

Choose a retained date range, CSV or JSON, and one ledger: monitor runs, incidents, notification deliveries, or notification attempts.

Included

Stable identifiers, states, timings, safe failure summaries, suppression reasons, and provider-acceptance evidence within the plan's retention window.

Excluded

Tokens, execution URLs, channel settings, subscriber addresses, raw request or response bodies, provider references, and customer payloads. CSV cells are neutralized against spreadsheet-formula execution.

Understand plan limits and billing state

Plan Monitor capacity Evidence retention Activation
Free 5 7 days Created with the workspace
Starter 50 30 days Owner-only monthly Paddle checkout
Pro 200 90 days Owner-only monthly Paddle checkout
Custom Managed 365 days Managed agreement

The owner of a Free workspace can choose a paid monthly plan, schedule cancellation for the end of the paid period, and resume before cancellation takes effect. See current plan prices. Checkout uses the workspace owner's account email. Paddle API verifies the subscription after checkout, cancellation or resume; unconfirmed requests remain pending and receive a daily background check. Contact support to change between paid plans. Custom is non-selectable and managed through support; other accepted members retain read-only billing visibility.

Workspace integration Team Evidence exports Billing