Contract owner
Sees only their own contracts.
- Pages
- Home, My contracts, Questions from legal, Renewals, Legal playbook
- Can start
- Send a contract to legal, Send an answer or a document
A contract lifecycle portal is where contract owners submit agreements for legal review, legal approves or rejects each one with a reason on the record, and a reminder goes out before a contract renews.
Pattern: RequestsDescribe it to Pory
“Our team leads send vendor contracts to legal before anything is agreed. Legal approves or rejects each one, and we want a reminder before any contract renews.”
Contracts
In plain English
Pory gives every contract owner and legal counsel a sign-in of their own. Each contract owner sees only their own contracts. It covers draft → review → approve. Contracts, questions from legal, supplier invoices, templates and guides and legal team live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
Contracts used to reach legal as forwarded email attachments, and approvals came back as "fine by me" with no note of what was checked. Legal counsel sees every contract on a board by status, opens one, reads the attached file and the owner's answers, and approves or rejects it, writing the reason on the record. The contract owner reads the answer on their contract instead of chasing legal in the hallway.
Auto-renewals used to be noticed on the credit card statement, a year too late to cancel. Each contract carries its renewal date and the date notice is due, and legal gets a reminder in their portal inbox and by email before it arrives, naming the contract and the date. There's time to renegotiate or give notice, instead of another year of a tool nobody opens.
Every person signs in to their own view. This is what each role in the demo gets.
Sees only their own contracts.
Sees every contract in the portal.
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
Renewals, expiries and overdue work, in an in-app inbox and by email.
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colors, your logo. Members see you.
Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited contract owners.