How Constructable Works
Permissions and Data Visibility
Constructable helps your organization give each person the access they need without exposing every project, record, or action. Your role, project access, record sharing, and the record's workflow state all affect what you can see and do.
Constructable helps your organization give each person the access they need without exposing every project, record, or action. Your role, project access, record sharing, and the record's workflow state all affect what you can see and do.
The access layers
Several controls work together to determine your access:
- Package and workspace availability determine whether your organization has a capability.
- Organization membership and role establish your organization-wide access and actions.
- Project membership and project access determine which projects you can enter.
- Permissions determine which tools, records, and actions you can use.
- Level-of-access choices can narrow a permission to records connected to you, such as particular projects, companies, meetings, RFIs, or Submittals.
- Record sharing and workflow state can further limit access to a Topic, document, draft, or unpublished item.
- Platform support affects where an available action appears for you.
Access through one layer does not bypass the others. For example, if you can view a published drawing during a site walk, you do not automatically have access to every RFI, Submittal, Quality Item, or Topic pinned to it.
Consistent visibility
Constructable applies your permitted record scope when it makes project data available and when Search and AI retrieve information. A direct URL, Thread, notification, or drawing pin still requires access to the underlying record.
Because of these checks, two people can have different but valid views. An administrator may see all RFIs, while a project partner sees non-draft RFIs and only their own drafts. A Topic can also be shared with a small group even when more people can view the drawing where it is pinned.
What this means for you
- If an action is missing, check package availability, platform support, permissions, access level, record state, and sharing.
- A notification or direct record link does not give you access to the record.
- You cannot use Search or AI to discover records outside your permitted scope.
- When possible, adjust the narrowest relevant permission or sharing rule instead of changing a person's broad role.
- Treat your current Roles and Permissions matrix as the authority because your organization may have customized its defaults.
Common boundaries
Permissions, visibility, status, and notifications answer different questions:
- Permission answers what you may access or do.
- Visibility or sharing answers which permitted audience can see a particular record.
- Status answers where the record is in its workflow, such as draft, published, open, or archived.
- Notification settings answer which accessible changes should alert you.
Changing notification settings cannot expose a record. Publishing a drawing does not publish its connected RFI, and sharing a Topic does not give you access to every record linked from it.
If something is missing
- Confirm that you are in the intended organization, project, and record, then check the workflow state.
- Check whether the capability is included and enabled.
- Check the person's project membership and project access.
- Review the specific permission and any level-of-access setting.
- Review the record's sharing, draft, archive, publication, or deletion state.
- Confirm that the action is supported in your current browser, device, and layout.
See Troubleshooting organization administration, Troubleshooting teams and directory, and Understanding drawing permissions and visibility.