Begin with one task someone can finish.

“We need a client portal” is a useful starting point, but it leaves the central decisions open. What will a customer do there? Which information does the team need? Who can make the next decision? A brief should answer those questions before it becomes a list of screens.

Choose one recurring workflow for the first release. For example: a customer submits a request with supporting information; a reviewer checks it; an approver records a decision. This example is illustrative, not a report of a client project.

Write the useful completion in plain language. “The approver can confirm the current request version and the customer can see the decision” is more reviewable than “a modern dashboard with approvals.” Identify any existing tool that remains the source of truth.

Starting sentence: “A [person] needs to [complete a task] using [record or information], so that [an observable result] is possible.”

Build a role table with a negative column.

Write down what each person may see and do. Then add what they must not access. The negative column makes assumptions visible: a customer seeing their own requests does not mean they should be able to discover another customer's files.

Illustrative role table — adapt every row to the actual workflow
RoleMay viewMay actMust not access
CustomerTheir own requests and shared filesCreate a draft, submit it and respond to questionsAnother customer's records or internal notes
ReviewerAssigned requests and relevant filesAsk for information and mark review readinessFinal approval unless explicitly authorised
ApproverThe current version and review contextRecord an agreed decisionUnrelated customer work outside their remit
OperatorOperational information needed for their roleManage assignments or access as agreedUnrestricted access simply because a menu says admin

The table is a requirements aid. The implementation must enforce permissions for the relevant requests and resources, not rely on hiding a button. OWASP recommends explicit permission checks, a default-deny approach and validation on each request. See OWASP's authorization guidance.

Include the account lifecycle: who invites a person, who changes their role, and what should happen to old links, downloaded information and active sessions after access changes. The exact controls and evidence depend on the product and its risks.

Turn the role table into a permission review.

Added

A role table becomes more useful when each row has an observable acceptance example. “Customers see their own files” leaves several decisions open: which file version, which link, and what happens after access changes? Write the resource and action together, then show one allowed journey and one refused journey against the same rule.

Use deliberately separate test accounts and non-sensitive fixture records. In this illustrative review, Customer A owns Request A and Customer B owns Request B. The names describe planning fixtures, not client accounts or a running NG Labs product. Ask the reviewer to record the expected outcome before a demonstration starts, so a surprising result cannot silently become the requirement.

Illustrative permission review — agree each expected outcome
Journey to reviewDecision to agreeEvidence to record
Customer A opens their own request and its current fileWhich record and version may this account retrieve?Fixture account, resource reference, expected visible state and observed result
Customer B follows a copied link to Request AWhat refusal is appropriate without disclosing another customer’s information?The agreed refusal and confirmation that protected content was not exposed
A reviewer attempts final approvalIs this role allowed to approve this resource, or only ask for a correction?The allowed action and the separate refused-action result
An approver receives an older file versionMay an earlier version still be approved, or must the person review the current version?The identified version and the agreed transition
A person returns through an old link after access is removedWhat happens to that link and the account’s existing access?The changed role, test conditions and observed result after the change

Decide who can set up each fixture and who may view the evidence. A useful review record identifies the tested release, role, resource, relevant state, expected outcome and actual outcome. Where a decision remains open, name its owner and leave the item unresolved. Avoid collecting passwords, session details or private customer files in the worksheet.

Also separate access within the application from information someone has already downloaded. Removing a role does not, by itself, establish what happens to an earlier exported copy. Agree the product’s download and retention expectations with the responsible people rather than implying that a menu change solves every information-handling question.

Keep the review proportionate to the product. These examples help a buyer and delivery team agree requirements; they are not a penetration test, exhaustive authorization test plan or security certification. Implementation-specific controls and risk review still need their own scope and evidence.

Download the blank permission review worksheet and use it alongside the role table above. Start with the first useful workflow, then add resource and state combinations that matter to that release.

Name the record and its allowed states.

A request, file or approval is more than a row in a dashboard. Decide which information belongs to it, which version is current and which states are meaningful. A compact state map can reveal a missing responsibility before design begins.

Draft → Ready for review → Needs a change / Approved → Closed

For every transition, name the person allowed to make it, the required information and the result shown to everyone else. Can a customer edit a submitted request? Does a changed file invalidate an approval? Can an operator reopen a closed item? Keep these decisions with the record rather than leaving them in an informal conversation.

Identify the authoritative source for fields coming from another system. A portal may display progress from an operational tool while keeping its own comments or decisions. The brief should distinguish those responsibilities instead of assuming every field can be edited in both places.

Give unresolved work an owner.

List the awkward cases alongside the intended journey. Missing information, an expired link, an old file version or a repeated click can each produce a different product decision. “Show an error” is rarely a complete requirement.

  • Missing information: what must be supplied, who can correct it and whether a draft can be retained.
  • Repeated action: how an accidental repeat is distinguished from a new intended request.
  • Changed access: what a person sees when a role or assignment no longer permits an action.
  • Failed update: whether the record stays pending, what can be retried and who investigates it.
  • Outdated version: which version a decision refers to and whether a new review is required.

If an integration is involved, identify its source, destination, trigger and access owner. Agree how a failed update becomes visible, how duplicates are handled and who confirms recovery. A named third-party product does not establish that its required access or interface is available.

Write acceptance as observable examples.

Agree the smallest useful journey and show how a person will demonstrate it. Include both a permitted action and an action that should be refused. Test information and accounts should represent the agreed roles without using live customer records by default.

  • A permitted customer creates a request and sees its submitted state.
  • A reviewer asks for a missing item against the correct request.
  • An approver records a decision against the current version.
  • A different customer cannot retrieve that request or file.
  • A repeated action does not create an unintended duplicate.
  • An unsuccessful external update remains visibly unresolved with a responsible owner.

Agree devices and browsers, keyboard journeys, visible labels, empty states and correction messages. W3C's forms guidance explains how labels identify controls and should be associated with them. See the W3C WAI labeling tutorial.

These examples are a starting point, not a security or accessibility certification. Add the product-specific reviews, test cases and operating requirements appropriate to the information and work involved.

Use the starting brief.

Copy the plain-text structure below or download the blank brief. Keep the first release bounded. Write down what stays manual and which proposed features are deferred.

Blank template

CLIENT PORTAL — STARTING BRIEF

Workflow / task:
People who use it:
Record, file or item:
Useful completion:
Information source and owner:

ROLE | MAY VIEW | MAY CHANGE / APPROVE | MUST NOT ACCESS
Customer:
Reviewer:
Approver:
Operator:

STATES
Draft → Ready for review → Needs a change / Approved → Closed
Who may make each change? What information is required?

EXCEPTIONS
Missing information:
Old file or version:
Repeated action:
Changed / removed access:
Failed external update:
Who is responsible for each unresolved case?

FIRST RELEASE
Included core journey:
Explicitly manual steps:
Deferred features:
Agreed devices and browsers:
Acceptance examples:

OWNERSHIP
Source, hosting and service accounts:
Data export and retention decisions:
Backup and restore responsibilities:
Release and ongoing support responsibilities:

This is a starting brief, not a complete specification or security assessment.
NG Labs — https://nglabs.cc/insights/client-portal-brief/

Decide who owns the product after release.

Confirm the repository, hosting, domain and service accounts, along with the person who can grant or remove access. Name who is responsible for data export, retention decisions, backup and restoration, routine updates and incidents. Record the release process and ongoing support scope.

A project brief should also identify its decision maker. If two teams disagree about access, source information or approval responsibility, resolve that decision before treating the feature as ready to build.

For a scope conversation, read about client portal development or custom web application development. You can email NG Labs with one task, the people involved and the existing tools. Leave credentials and private customer records out of the initial message.

References

The task, role and state examples above are original planning material from NG Labs. These primary references support the specific authorization and labeling points.