How grants, the agent in charge, and the Team area decide who sees and edits what.
Last updated: 2026-05-10
Access in Urbero is built from two grant types and one ownership marker. Everything else — what an agent sees on /units, whether the Edit button shows up, whether a photographer can upload — flows from these three signals.
Building assignment is view-only. It lets an agent or photographer see the units in that building. It does not let them edit anything.
Unit assignment is view plus edit. This is the only way an agent gets edit rights on a unit. Without a unit assignment an agent can look at the unit (if a building assignment is in place) but cannot change anything.
Why this matters: the building assignment is for visibility — onboarding an agent to a portfolio, giving a photographer access to walk a building. Edit rights are always granted unit by unit, so it's deliberate which units an agent owns.
Every unit can have an Agent in charge: a single named owner. The agent in charge is the one person responsible for the unit, distinct from a unit assignment.
A unit assignment can include several agents (many-to-one edit grant). The agent in charge is one person. Setting an agent in charge also creates a unit assignment for that person automatically and sends them a notification — they don't have to be granted edit rights separately.
A change of agent in charge is an audit event, so you can always answer "who owned this unit on October 4th?".
The Team area is where brokerage admins and owners manage members.
/team — the roster of brokerage members. This is the list page where you invite, manage, and offboard./team/assignments — a kanban for distributing work. Drag a unit between agents and the system updates the unit assignment./team/performance — the team-wide performance view. Rentals, days-on-market, and other agent KPIs in one comparable layout./team/[userId] — the per-agent detail page. The grants editor lives here, plus a KPI strip (rentals over 30 / 90 / 365 days, average days-on-market to close, deals closed-vs-lost, comments authored) and a 30-day activity feed. Visible to super-admin and to brokerage admins or owners of the agent's brokerage.Brokerage admins invite new members from /team:
/team.You cannot invite a brokerage owner from this flow. There's only one owner per brokerage, and ownership transfer is a separate action the current owner takes.
From /team, click Manage on the row, then Offboard. A confirmation dialog opens — confirm, and the system releases all their assignments and removes them from the brokerage.
The user record itself stays. Their name still appears on past leases, audit rows, and comments — offboarding is not a deletion, it's a removal of edit rights and a release of work.
From /team click into any agent to land on /team/[userId]. You'll see a profile header (name, role, contact, last active), the KPI strip (samples under three rentals hide the DOM number so a quiet week doesn't read as a statistical claim), an access scope summary, a 30-day activity feed, the grants editor, and a YTD commission card (admin and self only).
Only super-admin and brokerage admins / owners of the agent's own brokerage can open this page.
| Role | What they can do |
|---|---|
| Brokerage owner | Full edit in their brokerage. The only role that can promote admins and transfer ownership. Limit one owner per brokerage. |
| Brokerage admin | Manage members and assignments; full edit on every unit and building in the brokerage. Cannot promote admins or transfer ownership. |
| Agent | Edit only the units they're explicitly assigned to. View buildings via building assignments. |
| Photographer | Upload and edit photos on units flagged for a professional shoot, within buildings they're assigned to. |
| Landlord admin | Read-only on unit data; can invite and remove other landlord members for their landlord. |
| Landlord viewer | Read-only on unit data for the landlords they're tied to. |
| Super-admin | Manages brokerages, users, and landlords at the platform level. Cannot edit unit or building data — not even when using the "View as <brokerage>" support mode (see Dashboards). |
The super-admin restriction is load-bearing. The support cookie that flips chrome into a brokerage's operational view is chrome only — it narrows what you see, never widens what you can change. Tampering with the cookie cannot grant edit rights.