Cendryva
Join the waitlist

Create Your First Workspace

Use this workflow to stand up an organization that people can access with the correct scope on their first sign-in.

Availability: Plan-dependent5 min readLast reviewed September 3, 2026

Prerequisites

  • An active Cendryva account
  • Permission to create or administer an organization
  • The organization's display name
  • The operating timezone
  • Initial administrators or owners

Instructions

  1. Sign in to Cendryva.
  2. Create or select an organization.
  3. Enter the organization's human-readable name and timezone.
  4. Configure the operating cadence.
  5. Invite the initial team members.
  6. Assign the minimum necessary roles and permissions.
  7. Create departments, divisions, teams, or posts only as needed.
  8. Confirm that each user can access the expected workspace.

Expected Result

Users can access the organization according to their assigned roles and scopes.

Start Narrow

Model the operating unit you actually intend to review on a cadence — usually a company, subsidiary, or division. Additional structure can be added when a real reporting need appears.

Over-modeling the org chart before any statistics exist is the most common reason an early rollout stalls.

Important: Security Note

Do not grant administrative access merely to solve a navigation problem. Apply least-privilege access and review invitations before sending them.

About Interface Details

This article describes the workflow rather than exact button labels or menu locations, which vary by plan, role, and release. Follow the equivalent step in the application you are signed in to.

Troubleshooting

An invited user signs in but sees no organization.
Confirm the invitation was accepted with the same email address and that the user holds a role scoped to that organization.
Reporting periods look shifted by a day.
Check the organization timezone and the reporting period of the affected statistics; period boundaries follow the organization's configured timezone.
A user can open a page but cannot complete an action.
Page visibility is not permission. Review the user's role and organizational scope rather than granting broader administrative access.

Related Articles