Overview
Access is controlled through your organization’s directory (such as Azure AD, Okta, or Google Workspace) and synchronized with SpaceTI through SCIM or WorkOS integration.
If a user cannot see or book rooms in certain buildings, follow the steps below to verify and restore their access.
1. Check Group Membership in Your Directory
Open your organization’s directory management system (e.g., Azure AD, Okta).
Search for the affected user.
Review their group memberships.
Confirm that the user belongs to all relevant access groups (for example:
Building.A.Access
Building.B.Access
Each group corresponds to one or more buildings in SpaceTI.
If both building access groups are listed, proceed to Step 2.
2. Verify Directory Sync in WorkOS or Your SCIM Integration
Open your WorkOS Admin Dashboard (or equivalent SCIM integration tool).
Go to Directory Sync → Users and search for the same user.
Review the user’s group memberships in the synced data.
Confirm that both building access groups are present and active.
⚠️ If a group is missing, the directory sync may not have completed successfully — especially if the user was recently added, removed, or restored.
🛠 Fix: Restart provisioning or manually trigger a directory resync to ensure all group memberships are up to date.
3. Check Building Access in the SpaceTI Admin Panel
Open SpaceTI Admin → Users (or Access Management).
Locate the user profile.
Under Assigned Buildings or Access Rights, confirm the user has access to all relevant buildings.
If a building is missing:
Confirm that the user is in the correct group(s) in your directory.
Optionally, manually assign the building in SpaceTI (if your organization allows manual overrides).
4. Test Access
Ask the user to:
Log out and back into the SpaceTI app or web portal.
Refresh their profile and verify they can see and book rooms in all assigned buildings.
If they can access both buildings after this step, synchronization was successful.
Common Causes of Missing Building Access
Cause | Resolution |
User missing from one or more access groups | Add the user to the correct groups in your directory |
Directory sync incomplete or delayed | Restart provisioning or manually trigger a sync |
User recently deactivated or restored | Recreate or re-provision the user to ensure full resync |
Cached session or outdated app version | Have the user log out, clear cache, and log back in |
Best Practices
Keep your access groups well-structured (e.g., one per building).
Schedule regular sync reviews to ensure permissions stay aligned.
Encourage users to always log out and back in after major account changes.