Summary and recommendation
Building Engines user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
Building Engines is a commercial property operations platform targeting property managers and building operators.
When every app in your stack is evaluated for user lifecycle management, Building Engines stands out for its lack of public documentation on provisioning flows, admin console paths, and user types.
Teams should expect to rely heavily on vendor support rather than self-serve configuration.
Quick facts
| Admin console path | Settings / Administration > Users and Roles (exact labels vary by tenant) |
| SCIM available | No |
| SCIM tier required | Enterprise |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Can manage tenant settings, integrations, and user access. | Cannot grant capabilities outside the features enabled for the tenant. | Detailed built-in role names are not fully documented publicly. | ||
| Standard User | Can use the core product features exposed to their assigned role. | May not be able to manage tenant settings, integrations, or other users. | Exact privileges can vary by tenant configuration and contract scope. |
Permission model
- Model type: role-based
- Description: Building Engines appears to use role-based access for tenant administration and general product use, but the detailed permission matrix is not publicly documented in full.
- Custom roles: Unknown
- Custom roles plan: Not documented
- Granularity: Expect administrative access to be separated from standard user access, with exact scopes configured per tenant.
How to add users
- Log in as an administrator.
- Open settings or administration and navigate to users.
- Choose the add or invite user action.
- Enter the user's work email and assign the appropriate role.
- Save the user and complete any activation or SSO steps required by the tenant.
Required fields: Work email address, Role
Watch out for:
- Public documentation for user administration is limited, so exact labels may vary by tenant.
- If SSO is enabled, upstream IdP assignment may still be required before the user can sign in.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Unknown | Not documented |
| Domain whitelisting | Unknown | Automatic domain-based user add |
| IdP provisioning | Unknown | Not documented |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: Public docs do not clearly document whether users are disabled, deleted, or both. Treat lifecycle behavior as tenant-specific unless confirmed in-product.
- Open the users area as an administrator.
- Locate the user to offboard.
- Disable, revoke, or remove the account using the controls available in that tenant.
- Review any integrations, service accounts, or credentials associated with the departing user.
| Data impact | Behavior |
|---|---|
| Owned records | Tenant data remains in the workspace; public docs do not describe user-owned content semantics in detail. |
| Shared content | Shared content and workspace records typically remain available unless separately removed or reassigned. |
| Integrations | Review service credentials, workflow ownership, and integrations separately during admin offboarding. |
| License freed | Seat reuse behavior is contract-dependent and not publicly documented in detail. |
Watch out for:
- Offboarding should include token, integration, and service-account review, not just interactive login removal.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Named User | Access to the tenant features exposed to the assigned role. Seat entitlements are generally tied to the subscription contract. | Custom pricing; determined by contract and plan. |
- Where to check usage: Settings / Administration > Users and Roles
- How to identify unused seats: Review the tenant user list and any visible login or activity metadata. No public unused-seat report was verified.
- Billing notes: Building Engines is sold primarily through custom or enterprise contracts. Public seat pricing and detailed licensing terms are not broadly disclosed.
The cost of manual management
Because no native SCIM support exists and no public API for user management has been documented, every app that requires manual provisioning adds compounding overhead - and Building Engines is no exception.
Onboarding a new property manager or revoking access for a departing employee requires direct interaction with the platform's admin interface, which G2 reviewers flag as complex to navigate. Without automation, access changes are prone to lag, inconsistency, and audit gaps across your portfolio of tools.
The decision
When every app in your environment needs auditable, repeatable user provisioning, Building Engines presents a gap: no public admin console path, no documented bulk user management tooling, and a vendor-dependent setup experience. Teams with strict access governance requirements should confirm directly with Building Engines sales whether any provisioning automation is available.
Pricing is custom at the Enterprise tier; no lower-tier plans with documented user management features were found.
Bottom line
Building Engines offers property operations functionality but presents a low-transparency user management story: no public admin console path, no native SCIM, no documented API, and community signals pointing to a vendor-dependent setup experience.
Organizations with strict access governance requirements should engage Building Engines sales directly to understand what provisioning controls are available before committing to a deployment.
Automate Building Engines workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
