FuseBase Demo Organization
Copy to my workspace

T73 Permission and approval summary

Permission and approval summary

A security reviewer checking an approval record

Oakridge Property Management Revised summary, sign-off pending 2 approvals pending Client-visible

What the Oakridge maintenance triage pilot is permitted to do, who permitted it, and every approval and permission change on record, written for the security reviewer. Prepared by Sam Okoro, lead consultant at Fernway Automation, for the Oakridge security reviewer and Diane Foster, operations director at Oakridge Property Management. Record as of October 1, 2026.

Permission set in force
Read the maintenance inboxRead only, sending is not enabled. Approved by Diane Foster on Aug 26.
Create tickets in the coordinator queueCreate only, the pilot cannot edit or close tickets. Approved by Diane Foster on Aug 28.
Read the approved vendor listScoped to the vendor list only. Approved by Diane Foster on Sep 2.
Route after-hours requests to the on-call coordinatorApproved by Diane Foster on Sep 16. Applies to requests received between 6 pm and 7 am.
Dispatch vendorsNever a standing permission. Every dispatch waits for a named approver.
Not permittedMessaging tenants (excluded from scope), sending from the inbox, editing or closing tickets, and dispatching under a spend limit (not approved).

Sample template: the firm, people, clients and figures are fictional, and the embedded view holds synthetic sample records.

Permissions on record

The view lists each permission change and approval request on record, with the permission asked for, the approver, the decision and the date. Read the Approval decision column first. Approved rows are in force, Pending rows are not granted, and Declined rows are limits the pilot stays inside.

Before you share this page with a client

This sample view holds permission records for several clients, including Harrow Valley Clinics and Bluefin Insurance Brokers. Switch the embed to a view filtered to Oakridge Property Management before you send this page to the security reviewer or anyone at Oakridge.

Oakridge permission history

Every Oakridge permission and approval request on record, oldest first. The approver is the person named on the record, never a shared account.

DateRecordPermissionDecisionApproverOwner
Aug 26, 10:30Maintenance inbox read accessRead the maintenance inboxApprovedDiane FosterElise Fontaine
Aug 28, 15:00Coordinator queue ticket creationCreate tickets in the coordinator queueApprovedDiane FosterElise Fontaine
Sep 2, 14:00Vendor list read accessRead the approved vendor listApprovedDiane FosterElise Fontaine
Sep 16, 15:30After-hours routing ruleRoute after-hours requests to the on-call coordinatorApprovedDiane FosterSam Okoro
Sep 25, 16:00Vendor visit spend limitDispatch routine vendor visits under a spend limitPendingDiane FosterSam Okoro
Sep 30, 23:45Emergency vendor dispatchDispatch approved vendors after hoursPendingDiane FosterSam Okoro
Executions on record735logged through week 4, each against a permission
Named approvers2confirmation pending
Approvals pending2spend limit and emergency dispatch

Two approvals are waiting on Diane Foster

Vendor visit spend limit has been open since Sep 25. Sam Okoro asked whether routine visits below a limit could be dispatched under a standing approval, Diane has not set a limit, and the reminder of Sep 29 is unanswered, so every vendor visit still goes to a coordinator. Emergency vendor dispatch, a burst pipe report received at 11:40 pm on Sep 30, is held as a draft for Diane because vendor dispatch always waits for approval. Nothing is dispatched under either request until she decides.

Approval gates in the pilot record

The pilot record keeps each approval as a gate: approved with its date, or waiting for the named approver.

Live example from the Dashboards app, shown with Oakridge Property Management's demo data. Block dates move forward each week, so they can differ from the sample dates on this page.

Who may approve

DFDiane FosterOperations director, Oakridge Property Management, approver of record on every Oakridge permission
PRPriya RamanMaintenance operations manager, Oakridge Property Management, second named approver, confirmation pending
SOSam OkoroLead consultant, Fernway Automation, requests permissions and cannot approve them
IMInes MoreauAutomation engineer, Fernway Automation, checks that each run stays inside its permission
Approval rules
Who may approveTwo named Oakridge approvers. A shared account, the pilot itself and Fernway Automation staff cannot approve.
Needs a person every timeEvery vendor dispatch, including after-hours dispatch. Nothing is dispatched under a standing approval.
Standing approvalsRead access to the maintenance inbox and the approved vendor list, ticket creation in the coordinator queue, and routing after-hours requests to the on-call coordinator.
When an approver is unavailableThe second named approver decides once Diane Foster has confirmed them. Until then a request stays pending and nothing is dispatched.
Narrowing or withdrawingDiane Foster can narrow or withdraw any permission, and the record shows who did it and when.

Rejected in the first summary: a shared account listed as approver

The first version of this summary named a shared account as an approver. The Oakridge security reviewer rejected it because a shared account cannot show who decided. Sam Okoro replaced it with two named approvers and asked Diane Foster to confirm them. Until Diane confirms Priya Raman as the second name and the reviewer signs off, this revised summary stays marked pending and the second phase waits behind the review.

How one approval is recorded

The example follows the burst pipe report of Sep 30. The run cannot dispatch on its own, so it holds a draft and asks a named approver. Whatever the answer, the record gets one entry.

sequenceDiagram
    participant R as Triage run
    participant L as Pilot record
    participant D as Named approver
    R->>L: Log the request and the permission it needs
    R->>D: Hold a draft dispatch and ask for approval
    alt Approved
        D->>R: Approved, with name and time
        R->>R: Dispatch the approved vendor under that approval
    else Declined or no answer
        D-->>R: Declined or no reply
        R->>L: Keep the draft held and record the decision as declined or pending
    end
    R->>L: Record identity, scope, time and result

Retention and data handling

What every execution records

Each of the 735 executions logged through week 4 is recorded against a permission with identity, scope, time and result. The full six-week count goes into the final summary after the pilot closes on Oct 11. The reviewer can start from any action and reach the permission it ran under and the person who approved that permission, without asking Fernway Automation to pull the data.

Retention is set in the engagement agreement

How long these records are kept, where they are held and how personal details in requests are processed are contractual matters for Oakridge and Fernway Automation. This summary does not set them. The reviewer should read the retention terms in the engagement agreement alongside this page.

Open data handling point: large photo attachments

Photo attachments above the inbox size limit could not be opened, so 14 requests were classified from the text alone and routed with a note that images were not reviewed (Large photo attachments, owner Ines Moreau, Exception open). The fix is blocked until the mail administrator raises the limit, requested Sep 24. Opening those images widens what the pilot reads, so it is recorded as a permission change and approved by Diane Foster before the limit is raised.

Reviewer checklist

For the Oakridge security reviewer
✓Every Oakridge permission names a scope and a named approver
✓No shared account is listed as an approver
✓Vendor dispatch always waits for a named approver
✓Every execution shows identity, scope, time and result
Diane Foster confirms Priya Raman as the second named approver (Sam Okoro asked, confirmation outstanding)
Diane Foster decides the vendor visit spend limit and the emergency vendor dispatch
Retention and data handling terms checked against the engagement agreement
Reviewer signs off the revised summary (Sam Okoro sends it once the approvers are confirmed, planned Oct 6)
Sign-off

The revised summary goes to the security reviewer with the two named approvers as soon as Diane Foster confirms them. The conversion checklist review with Diane, after two weeks of the new tenant form, is planned for the week of Oct 12.

How to use this template

Keep one summary per pilot and client. Fill the variables below from the permission record, and filter the embedded view to the same client before the summary goes to the security reviewer.

VariableMeaningRequired
{{client.name}}Client organization the pilot runs forRequired
{{record.as_of_date}}Date the permission record was last checkedRequired
{{permission.set_list}}Permissions in force, each with scope and approval dateRequired
{{approver.primary_name}}First named client approverRequired
{{approver.second_name}}Second named client approverRequired
{{reviewer.name}}Client security reviewer who signs offOptional
{{retention.clause_reference}}Clause in the engagement agreement that sets retention and data handlingRequired

If a required value is missing, show Needs review in its place and hold the summary; never fill it with a guess. If the permission record is unavailable, show Unavailable instead of the table.

The live Dashboards blocks on this page show the Oakridge Property Management demo profile. Point each block at your own client's profile, or remove it, before you share the page. Filter the embedded view to the same client as well.