Who Can Do What

Seeing a checklist starts with being able to see the transaction, and per-task visibility narrows things from there. Answers to the common questions about admin-only tasks, why a user can't see a checklist that's been added to a file, and who sees @...

Access decides who can see a transaction's checklist and each task on it — and in Pipeline, that comes down to who's on the transaction and the visibility set on each task. Introduction A checklist can hold work for four different people, and m...

Two permissions govern checklists, agents can agent-check tasks while only admins complete them, and building templates is admin territory. Answers to the common questions about letting agents add checklists, who can build templates, editing due dat...

Permissions decide what someone can do with checklists: apply them to transactions, build and edit templates, and check tasks off. You set them per user, per location. Introduction Two people can open the same transaction, see the same checklis...

A transaction coordinator lives in your checklists. One permission decides whether they can actually work them. Introduction Your TC runs the file. They chase the documents, check the boxes, and keep the deadlines honest, which means they spend...

Checklist templates belong to a location. That one field is what lets each office run its own process without stepping on anyone else's. Introduction Offices aren't interchangeable. A Texas closing doesn't need the Arkansas disclosure, a commer...