Understand how access works on IPX — the three access levels (Portfolio Admin, Location Member, Project Member), the three permission bundles (View, Download, Manage), optional Billing access, how access cascades, and how projects keep data separate within a location.
Sharing on IPX means giving someone access to exactly what they need — your whole portfolio, a single building, or one specific project — and choosing what they can do there. This guide explains how access works so you can pick the right setup every time. When you're ready to act, see Invite teammates, Share a location or project, Change or reduce access, and Manage members & invitations.
Every grant of access answers three questions: where can they work, what can they do there, and can they see costs.
When you invite someone, you first choose their level. Access cascades downward — the higher the level, the more they see.

A Portfolio Admin sees everything. A Location Member sees all projects at their location. A Project Member sees only their project. Granting someone a lower level never exposes anything above it — a Project Member can't see other projects, and a Location Member can't see other locations.
For Location and Project members, you also choose a permission bundle. Each bundle includes everything in the one before it.

A Location Member with Manage has full control over all projects at that location — current and future — and can invite Project Members there. A Project Member with Manage can only act within their one assigned project.
Billing is a separate, optional add-on that you can turn on for any role. It adds access to invoices and payment methods — across the whole company for a Portfolio Admin, or for the specific location or project for a Location/Project Member. Leave it off and the person never sees pricing or payments.

A location can hold several projects — a SCANIT scan, a BIMIT model, a Site Monitoring campaign. Projects are the unit that keeps data separated within a single building.
New projects are visible to everyone with access to the location. For sensitive work, an admin can restrict a project so only the people assigned to it can see it — everyone else won't even know it exists. This lets one building hold, say, BIM deliverables and confidential site-monitoring data without one team seeing the other's.
This is why you rarely need duplicate locations: instead of "383 Madison" and "383 Madison SM," you keep one location with two projects and assign different people to each.