Who Can Do What

How much rope do your agents get on their own files? Three separate controls answer that, and mixing them up is why the setting you're looking for seems to be missing. Introduction Offices usually arrive at this with a specific ask — let them ...

Escrow needs the closing package, your client wants a copy of everything, the lender wants three disclosures. None of them needs a login — and here's how to get them what they're asking for anyway. Introduction Pipeline has no external role. Th...

Access comes from being added to a transaction or from a location-wide admin permission, and outside parties don't get a login. Answers to the common questions about why an agent can't see a file, sharing a single transaction, and access after a tra...

Access decides who can open a transaction and see what's inside it — and in Pipeline, that comes down to who's on the transaction and who can view everything in its location. Introduction A transaction in Paperless Pipeline is visible to a spec...

You set permissions per user and per location, a few actions belong to the master admin alone, and Pipeline adds its own field rules on top. Answers to the common questions about closing transactions, deleting them, downloads, and editing names or M...

Permissions decide what someone can do to a transaction: create it, edit its fields, change its status, or delete it. You set them per user, per location. Introduction Two people can be inside the same transaction and still not be able to do th...

Independent contractor agreements, license renewals, mentorship agreements — the paperwork that isn't a deal still needs a home with real permissions. A transaction can be that home. Introduction There is no way to attach a document to a person...

When an agent can't change a certain field on a transaction, Pipeline is doing its job — limiting edits by the agent's permissions and by built-in rules that protect a transaction as it moves forward. What's Happening Once a transaction exists,...