Create your first organization

After signing up for Incido, a short onboarding flow creates the base workspace your team uses for public communication. This page explains what gets prepared and which non-privileged next steps help you move into daily operations quickly.

Before you start

You need a valid email address to register and an organization name you can recognize internally. You can update organization-level defaults later in Organization settings and config transfer.

Sign up and create the organization

Open the Incido Dashboard and complete sign-up with your email address and password. During onboarding, you provide an organization name and baseline preferences such as locale and timezone. After completion, your organization is created and ready for operational setup.

Continue with operational setup

Once onboarding is complete, the most useful next step is defining customer-visible service structure in Components and taxonomies. From there, move to Status pages to configure where incidents and maintenances are published, then use Incidents and Maintenances for day-to-day communication. When you plan webhooks, monitors, or API automation, add Best practices early so deduplication keys and status page layout stay aligned with how your team responds.

If you need context on permissions and team access before collaborators begin publishing updates, read Users, roles, and invitations. If you are evaluating feature availability in your workspace, read Billing and plan changes.

What changes on the public frontend

Onboarding itself does not publish incident or maintenance content to customers. The customer-visible impact starts when your team configures status pages, components, and communication workflows. Locale choices made during setup influence language defaults for future customer-facing content.

Operational effects

Onboarding establishes baseline defaults that downstream workflows rely on, including language and timezone context. If these defaults are incorrect, operational communication can look inconsistent across incident and maintenance updates. Aligning these settings early reduces rework when your team begins publishing frequent updates.

Troubleshooting

Dates and times look wrong after setup. Review timezone settings in your profile and organization defaults, then reload the Dashboard to ensure timeline timestamps match your operating context.

You completed onboarding but do not know the next step. Continue with Components and taxonomies and Status pages, then validate the publication flow with a test update in Incidents.