👤 User

Users

People who access an organization or participate in booking workflows.

Overview

Users are the people who sign in to Skedular, belong to one or more organizations, and perform actions such as booking resources, managing locations, or administering workspaces. Their organization role determines which actions and information are available to them.

Supported in✅ Skedular Teams✅ Skedular Spaces✅ Skedular Host

How Users Work

A user creates or receives an account, accepts an organization invitation when required, and joins the organization as a member. The organization assigns a role, and the user then signs in to perform the actions allowed by that role. A user can belong to multiple organizations, with a different role in each. Removing the organization membership ends that user’s access to the organization.

Where This Concept Fits

👤 User
🔑 Authentication🪪 Profile

Product Support

  • Skedular Teams: Users are private organization members. Owners, Administrators, and Members can have different responsibilities, and members can join teams.
  • Skedular Spaces: Users operate marketplace organizations as Owners, Administrators, or Members. Customers have a separate customer-facing booking relationship and do not manage the organization.
  • Skedular Host: The current model has one owner for the host organization. Additional organization users are not supported in this simplified workflow.

User Identity

A user is identified by their account and organization memberships. The same person can belong to several organizations. Each membership stores its own role and status, so access is evaluated in the context of the organization being used.

Organizations and Roles

Organizations are the ownership boundary for users, locations, resources, settings, and bookings. A user can belong to multiple organizations, but a role in one organization does not automatically grant access to another.

Owner

Owners have full control of an organization, including settings, billing, locations, resources, users, teams, bookings, and role assignments.

Administrator

Administrators handle day-to-day operations such as locations, resources, bookings, teams, users, and operational settings. Their access may not include billing or ownership controls.

Member

Members use the organization. Depending on its settings, they can create and manage bookings, view availability, and join teams, without access to administrative functions.

Authentication and Permissions

Users sign in through Skedular’s configured identity provider. WorkOS is supported as an identity-provider integration where it is configured. Authentication confirms who the user is; the organization’s assigned role determines what that user can do. This page describes the relationship only. See the product guides for the available sign-in workflow.

User Lifecycle

Users move through a simple organization membership lifecycle:

  • Invited: An organization asks a person to join.
  • Joined: The person accepts and becomes an organization member.
  • Active: The member signs in and uses the permissions granted by their role.
  • Removed: The membership is removed, ending access to that organization.

Product Differences

👥 Skedular TeamsPrivate workplace members can join teams and coordinate workplace bookings.
🛒 Skedular SpacesOrganization users operate locations, products, customers, bookings, and marketplace settings.
🏠 Skedular HostA single owner manages the host organization and its places through a simplified workflow.

What Belongs to a User

🏢 OrganizationsOwnership boundaries that grant a user access.
🔐 RolesOrganization-specific responsibilities and permissions.
👥 TeamsGroups a user can join in Skedular Teams.📅 BookingsReservations a user can make or manage.
🛡 PermissionsAccess derived from the assigned organization role.
🪪 ProfileAccount information used to identify the user.

Typical Workflow

1Invite User2Accept Invitation3Join Organization4Assign Role5Book Resources6Use Skedular

Best Practices

  • Assign the least privileged role needed for the work.
  • Review administrator access regularly.
  • Remove users who no longer need organization access.
  • Keep team membership current in Skedular Teams.
  • Keep user account details accurate.

Things to Know

  • A user can belong to multiple organizations.
  • Roles are assigned per organization.
  • Permissions come from the assigned role.
  • Users can create bookings when their role allows it.
  • Teams are available only in Skedular Teams.
  • Marketplace customers have a customer-facing relationship, separate from organization administration.
  • Skedular Host currently uses a single-owner organization model.

Frequently Asked Questions

What is a user?

A user is a person with an account who belongs to an organization or participates in a booking workflow.

Can a user belong to multiple organizations?

Yes. The same person can belong to multiple organizations, with a different role in each.

Can I change a user’s role?

An owner or authorized administrator can manage organization membership and assign roles when permitted.

What happens when I remove a user?

The user’s membership is removed and access to that organization ends. Existing booking records may remain part of the organization’s history.

Do marketplace customers count as organization users?

Customers can make marketplace bookings, but they are separate from the organization members who administer the marketplace organization.

How do users sign in?

Users sign in through the identity provider configured for their Skedular environment. WorkOS can provide that identity-provider integration when configured.

Continue Learning