What Contract Directory does in Proplix
Contract Directory is part of Proplix Stakeholder Portals and is designed to manage contract table as part of Contracts & Sales. It stays connected to the relevant portal relationship or stakeholder account, so the team can work from one controlled record instead of recreating the same information in inboxes, spreadsheets or notes.
Contracts, contract tables and sales attachments. In practical terms, Contract Directory supports contracts, contract tables and sales attachments. Where the same context matters to role-specific portal access, records, payments, contracts and communication, Proplix can reuse the existing record while permissions and workflow state govern what each user can see or change.
Why this capability matters for stakeholder portals
Operational workflows become unreliable when contract directory is handled differently by each team member. Self-service exposes the wrong relationship, file, financial record or administrative action. As volumes grow, that creates repeated checking, inconsistent handovers and duplicated data entry.
Using Contract Directory inside Proplix reduces that ambiguity by keeping the action close to the portal relationship or stakeholder account and the wider stakeholder portals workflow. The objective is to make existing work more predictable, reviewable and easier to hand over.
Where Contract Directory adds operational value
This section focuses on the specific operational context for this capability.
The operational question
Contract Directory is most useful when the team needs to manage contract table as part of Contracts & Sales while avoiding a situation where self-service exposes the wrong relationship, file, financial record or administrative action. The capability gives that situation an explicit place in the workflow instead of leaving staff to infer the answer from unrelated activity.
What good control looks like
A useful record should show the relevant portal relationship or stakeholder account, current workflow state, material evidence and any authorised decision that affects role-specific portal access, records, payments, contracts and communication. Exceptions should remain visible rather than being hidden by the normal path.
How Contract Directory fits into the workflow
The exact path depends on the user role, but the source record, evidence, permission or decision state and downstream handoff should remain connected.
- 01
Start from the correct context
Open the relevant portal relationship or stakeholder account before using contract directory. Starting from the authoritative record reduces the risk of applying the action to the wrong case or record.
- 02
Confirm the required information
Review the fields, state and portal-visible records, relationship checks, files, invoices and contract context needed for the action. Keep missing or contradictory information visible for review.
- 03
Use the structured Proplix control
Carry out contract directory through the relevant Proplix workflow so the result is recorded consistently instead of relying on free-text notes or local conventions.
- 04
Review connected outcomes
Check the role-specific portal access, records, payments, contracts and communication and any connected document, financial, communication or reporting view so downstream users receive a coherent state.
- 05
Retain a reviewable history
Keep significant changes and authorised portal access and stakeholder action connected to the record so a later user can understand what happened and why the workflow progressed or stopped.
What this feature helps the team control
Connected source record
Keep contract directory attached to the authoritative portal relationship or stakeholder account instead of maintaining another independent copy.
Permission-aware workflow
Make the current state clear while limiting sensitive actions and information to authorised roles.
Evidence and exceptions
Keep portal-visible records, relationship checks, files, invoices and contract context close to the workflow and surface incomplete, rejected or exceptional states for review.
Downstream consistency
Reuse the same operating context across role-specific portal access, records, payments, contracts and communication, communications and reporting where appropriate.
What this looks like in practice
Consider a normal operating case where the team needs to manage contract table as part of Contracts & Sales while avoiding a situation where self-service exposes the wrong relationship, file, financial record or administrative action. An authorised user handles Contract Directory from the relevant portal relationship or stakeholder account instead of opening a separate spreadsheet, creating an unrelated note or relying on an inbox-only instruction.
The immediate benefit is continuity. Another colleague can see the current position, the connected context and what is expected next. If the record later moves into role-specific portal access, records, payments, contracts and communication, the receiving team starts from the same controlled information rather than asking users to supply the same facts again.
How to introduce Contract Directory into a live operation
A strong implementation defines the source record, responsible role, exception path and audit requirement before the workflow is used at scale.
Before rolling out Contract Directory, agree the business meaning of the capability in plain language. Define who owns the underlying portal relationship or stakeholder account, which event should trigger the action and which role is responsible for reviewing or approving the result.
Identify the authoritative source for the values used by contract directory. Reuse existing Proplix data where appropriate instead of creating another copy simply because a different screen needs to display it.
Test the normal case and the main exceptions before relying on the capability at scale. Include missing information, rejected or expired evidence, changes after approval and at least one case where the workflow should stop rather than progress.
Built for authorised teams responsible for stakeholder portals
These capabilities support the people who create, review, approve or rely on this part of the Proplix operating model.
Keep data quality, permissions and authorised judgement aligned
Data quality remains important. Authorised users should keep the underlying portal relationship or stakeholder account current and resolve material inconsistencies close to the point where they arise.
Permissions should reflect responsibility. Users who can change significant workflow state, financial information, evidence or compliance outcomes should have access appropriate to their role.
Proplix portals expose controlled views of operational data. They do not replace identity governance, privacy decisions, contractual controls or authorised financial processes.
Related features in Stakeholder Portals
These related pages sit close to Contract Directory in the wider stakeholder portals architecture.
Technical flow & related Help Centre guides
Start with the primary guide for this capability, then use the related maintained guides for the surrounding workflow, evidence, access or handoff.
Questions about Contract Directory
What is Contract Directory in Proplix?
Contract Directory is a Stakeholder Portals capability designed to manage contract table as part of Contracts & Sales, with the action kept inside the wider stakeholder portals record.
When is Contract Directory most useful?
It is particularly useful when the team needs to manage contract table as part of Contracts & Sales while avoiding a situation where self-service exposes the wrong relationship, file, financial record or administrative action. A structured workflow gives authorised staff a shared current position without reconstructing context from separate systems.
Who should use or review Contract Directory?
The exact users depend on your organisation, but access should be limited to the authorised roles responsible for the relevant source information, review, decision or handoff.
Does Contract Directory replace professional or legal judgement?
Proplix portals expose controlled views of operational data. They do not replace identity governance, privacy decisions, contractual controls or authorised financial processes.
See how Proplix can structure stakeholder portals
A walkthrough can focus on the workflows, evidence, access and handoffs relevant to your organisation.