Roles & permissions

Organization vs. project membership

Construvex has two levels of membership:

• Organization members belong to your company as a whole. Their role applies across the organization — the right level for owners, admins, and anyone working across several projects.
• Project members are added to one project at a time — the right level for people who only need access to a single development, like a site engineer on one site.

A person can hold an organization role, project roles on one or more projects, or both; what they see is the combination. A project without an assigned role for someone simply isn't accessible to them — access isn't inherited just because they belong to the organization.

Inviting members

At the organization level: go to Settings → Members, select Invite Member, enter their email and a role, and send. You'll only be offered roles you're allowed to grant — for example, an Admin can invite Managers and Members but not another Owner.

At the project level: open the project, go to its Settings → Team, select Invite Member, and choose a project role. Use this when someone — a site supervisor, a local sales person — should only ever see that one development.

Tip: Invite people at the narrowest level that covers their job. It's easier to add a project later than to unwind broad organization access.

Roles and how permissions group by suite

A role is a named bundle of permissions. Construvex ships system roles you can assign right away, and lets you build custom roles when those don't fit.

Organization roles (broadest to narrowest): Owner (full control, including billing) → Admin (manages projects, members, settings) → Manager (views and edits projects day to day) → Member (basic access, usually paired with project roles).

Project roles (broadest to narrowest): Project Owner (full control of that project, including its team) → Project Manager (manages day-to-day content) → Project Member (can edit content) → Project Viewer (read-only).

Every permission belongs to one of the three suites — Construction (projects, phases, buildings, units, progress, approvals), Sales (customers, deals, payments), or Settings (members, roles, RERA/jurisdiction configuration, templates, billing). When you create or edit a custom role, its permissions are laid out grouped by suite — so you can build, for example, a role that manages Sales deals, only views Construction progress, and has no Settings access at all.

To create a custom role, go to Settings → Roles, select Add Role (or duplicate an existing role to start from its permissions), name it, and for each suite choose which actions it can perform. System roles can't be edited or deleted — build a custom role if you need something different.

Assigning and editing a member's roles

Go to Settings → Members and find the person (or open Team from within a project). Use Edit Role to change their organization role, or the project's team page to change or remove a project role. From the organization member's edit screen you can also review and adjust their role across every project they belong to in one place, and apply a role to all their projects at once when setting up several at a time.

Warning: Removing someone's role, or suspending their account, revokes their access immediately. Use suspension for a temporary pause and removal once someone has left for good.

Every role change, invitation, suspension, and removal is recorded in your organization's activity log, so you always have a trail of who changed what.

How plans differ in access

Construvex's Starter, Growth, and Professional plans use the same roles and permissions model — custom roles, suite-grouped permissions, and project-level access all work identically regardless of plan. Where plans differ is how many people you can add: higher plans support larger teams, so as your organization grows you may need to move up a plan to keep inviting members. For exact team-size limits, contact us.

Where to go next

• Getting started — creating your organization and inviting your first team
• Core concepts — the Project → Phase → Building → Unit hierarchy project roles apply to