Main / Blog / Role-based access control for corporate real estate, down to a single building

Role-based access control for corporate real estate, down to a single building

  • Date: October 21, 2026
  • by Maria Vasilyeva

A workplace team buys occupancy analytics. Six months later finance wants lease accounting, a portfolio team wants transaction approvals, and regional managers want their own sites. Then someone asks the question that stalls the whole thing: can we let the Frankfurt manager edit German leases without showing them the entire European portfolio?

If the answer is no, one of three things happens. People share logins. Someone gets access to rent and break terms they have no business seeing. Or a department gives up and buys a second system, and the portfolio view everyone wanted is gone.

Access Management v2, released this week, is built to make the answer yes.

Why Basking takes access control further

Different teams need different levels of access to the same portfolio. Finance works with lease accounting, workplace teams analyse occupancy, regional managers oversee their own buildings or markets. All of them still need to work inside one connected platform.

That is why we built Access Management around flexibility rather than a fixed set of permissions. At Basking, access is defined across two dimensions:

Then it answers questions against that model and produces outputs you can take into a meeting:

By function: Lease Administration, Lease Accounting, Occupancy Analytics, Transaction Approvals, or Document Processing.

By scope: The entire portfolio, a specific region, or a single building.

A finance team can manage lease accounting across the portfolio without ever opening occupancy data. A regional manager can work on leases for their own sites without seeing commercially sensitive terms from other markets.

The goal is simple: give every team access to exactly what they need, without compromising security or the single portfolio view everyone is working from.

What you can now do that you could not before

Roles are assigned per product, across Occupancy, LeaseOps, Lease Accounting, Flow, Docs AI and Access Controls. Each one carries its own scope: the whole portfolio, a region such as EMEA, or a single building.

Because the two are set independently, access finally matches how the work is actually divided:

Finance

Every site

Edits lease accounting for the whole portfolio.

Never sees occupancy data

Workplace team

Every site

Analyses occupancy across the whole estate.

Cannot open a lease

Regional manager

Their country only

Edits leases and approves transactions for their own sites.

No view of other regions

External advisor

One building

Views a single site for the length of the engagement.

Nothing beyond that site

None of this needs a workaround, a separate workspace, or a shared login. Permission and scope are set per product, so changing one never touches the others.

Two things that decide whether IT signs off

Granular roles are only worth as much as their enforcement and their upkeep.

Permissions are enforced on the server. Every request is checked against the user’s roles and scopes server-side, so access cannot be widened from the browser. Hiding a menu item is a design choice; refusing the request is the security control, and it is the one a security review asks about.

Administration takes minutes, not a ticket. Inviting users, managing groups and reviewing who can see what all happen in one place. Onboarding a new regional team means assigning a group, not configuring people one at a time, and the right to manage access can itself be scoped, so a regional administrator never gains global control.

Common questions

Can different teams have different permissions in the same workspace?
Yes. Roles are assigned per product, so a finance team can work in Lease Accounting while a workplace team works in Occupancy, with no overlap.

Can access be limited to specific buildings?
Yes. Each role is scoped to the whole portfolio, a region, or an individual site.

Can someone have edit rights in one product and view-only in another?
Yes. Access level and scope are set independently for each product.

Who can change permissions?
Only users with a role in Access Controls. That permission is itself scoped, so it can be delegated to a regional administrator without granting global control.

Does this work with SSO?
Yes. Access Management v2 governs what a user can do after authentication, so it sits alongside single sign-on rather than replacing it.

One platform, every team

See what this looks like on your portfolio

We’ll map your sites against who needs which data — finance, workplace teams, regional managers — and show how access works by product and by location, down to a single building. No sensors, no new data collection project.

Read more

Get started

If you want to know more about how our product works or have additional questions, please reach out to us: