In this section · 3 articles

Someone can't see or change Property CRM records

Work out why a team member can't see a client, property, requirement or inquiry, or can't add or change one: the workspace they're in, their membership, their role, or the record itself.

Applies to
Property CRM 5.1 and later
Who can do this
Administrator
Permission
feature.core.user.edit
On this page

Symptom

A team member says one of these:

  • A record they expect isn't in the list, or opening it says This client could not be opened.
  • A menu entry, a button such as New Client or Edit Property, or a whole card is missing.
  • Saving is refused with a message such as Choose a business before making this change.

Ask which record, what they tried, and the exact message.

Tip: Property CRM roles never hide records from each other. Within a business, everyone with a Property CRM role sees every client, property, requirement and inquiry, whoever they're assigned to. Assigned To says who works a record, not who may see it.

Check these, in order

1. They're working in another business

Every record belongs to the workspace it was created in, and people see the records of the workspace they're working in. Fix: ask them to open Workspace in the header and choose the record's business. See Switch workspace.

2. They're in All Workspaces

In All Workspaces they can read the records of every workspace they can enter, but not add or change any. There's no New Client button, edit buttons are hidden, and a save is refused:

MessageWhere
Choose a business before making this change.Properties, requirements, inquiries, and actions such as Convert or Assign
Clients cannot be saved right now: either no single business is in force, or the party directory is read-only here.Clients

Fix: switch to one business, then try again.

3. They aren't a member of the business

People can only enter workspaces they're active members of, so they never see that business's records. The same applies to assigning work. Choosing someone outside the business is refused with That person does not work in this business. for an inquiry, or That agent does not work in this business. for a property. Fix: add them to the workspace. See Create a workspace.

4. Their role doesn't allow it

Each Property CRM role allows different things. Menu entries and buttons the person isn't allowed to use aren't shown.

RoleCan't
Property CRM ViewerChange anything.
Property CRM TelecallerChange clients, properties or requirements, convert inquiries, or open the timeline or the settings.
Property CRM AgentDelete records, assign inquiries or requirements, or complete a sale or rental.
Property CRM ManagerPermanently delete records, or delete several at once.

A few things depend on a second permission:

  • The Matches card on a requirement needs feature.pcrm.property.list, and on a property feature.pcrm.requirement.list.
  • The Timeline shows only the kinds of record the person can list. With none, it says There is nothing here you are allowed to see. If they can list a kind of record but not view one, the preview says they can see the event but not open the record.
  • Unassigned, on the dashboard and the timeline, needs feature.pcrm.inquiry.assign.
  • Changing Assigned To in the inquiry form also needs feature.pcrm.inquiry.assign. Without it the field is read-only, and an inquiry they add arrives unassigned.

Fix: give them the role that fits. See Give people a Property CRM role. If your Laramin has the Roles & Permissions add-on, check Effective access to see where each permission comes from. See See why someone can do something.

5. Their role applies somewhere else

With the Roles & Permissions add-on, a role can be given in one workspace or one team only. It then works only while the person is in that workspace or team. Fix: give the role in the right scope, or Global. See Give someone a role.

6. They can't enter Property CRM at all

The Property CRM experience is offered to people with Enter Property CRM (feature.pcrm.workspace.enter). Every Property CRM role has it. The dashboard also needs feature.pcrm.dashboard.view. Fix: give them a Property CRM role, or both permissions. See Choose which experiences a user can enter.

7. The record itself can't be changed

Some records refuse changes whoever you are:

What they seeWhy
That record belongs to a different business than the one you are working in.The record is another business's. Switch to it.
That business is no longer in service.The workspace was archived. Nothing can be added to it.
A converted inquiry cannot be moved back.Converted is final.
A client without an Edit button, marked Data erasedThe person's data was erased.
This client could not be opened, with The record may have been merged away, or it belongs to a business you are not in.Two client records were merged, or the client belongs to another business.

Clients are never deleted in Property CRM. A relationship that ended is marked Relationship ended and still opens.

8. The Clients list is empty for everyone

The list says The party directory is not available. Clients live in the Organization add-on's directory. Fix: check that the Organization add-on is installed and turned on. Properties, requirements and inquiries keep showing their clients' names meanwhile.

Still not working?

Sign in as the person to see exactly what they see. See Sign in as another user. Then raise a ticket from Support Center in your Laramin app. Include this page's link and what you checked.