Share a request
Send a request to a colleague, or give someone outside the business a read-only link that expires.
Share on a request page offers two different things that are easy to confuse: a link that still requires a Trabalance sign-in, and a public link that does not.
The menu
| Item | What it does |
|---|---|
| Create public link | Mints an expiring, read-only web page for this request and copies its address to your clipboard. No sign-in needed to open it. |
| Copy internal link | Copies the address of the request page you are on. It only opens for people who can sign in and are allowed to see the request. |
| Opens WhatsApp with a one-line summary — title, amount, status — and the internal link. | |
| Opens your mail client with the same summary as the subject and body. | |
| Copy for Slack | Copies that summary block so you can paste it into a channel. |
| More options… | Your device’s own share sheet, where it offers one. |
WhatsApp, Email, Copy for Slack and Copy internal link all carry the internal address. Someone without an account, or without rights to that request, will hit the sign-in screen. If the recipient is outside the business, use Create public link.
Creating a public link
Trabalance first checks that you are allowed to read this request. The link never carries more access than you already had.
You are told it has been copied and when it expires. If your browser blocks the clipboard, the address is shown to you instead so nothing is lost.
It is an ordinary web address. Anyone holding it can open the page; nobody else can.
| Property | Value |
|---|---|
| Lifetime | Seven days from the moment it is created. |
| How many at a time | One per request. Creating a new link immediately kills the previous one. |
| Sign-in | None. The address itself is the credential. |
| What it can do | Read one request. Nothing else — it is not a way into the app. |
| Search engines | Excluded, and the page is never cached. |
Anyone who has the address can read the request, so send it the way you would send a password — to one person, on a channel you trust. Trabalance stores only a fingerprint of it, never the address itself, so a leak of the database can never produce a working link. Equally, nobody can recover the address for you: if you lose it, create a new one.
Killing a link early
Creating a fresh public link on the same request revokes the old one on the spot. That is how you cut off a link you have sent to the wrong person: open the request, choose Create public link again, and the previous address stops working immediately.
What the recipient sees
The public page shows the request and nothing around it — no menu, no sidebar, no route into Trabalance.
| On the page | Notes |
|---|---|
| Your business name | So the recipient knows who sent it. |
| Workflow and request number | For example, Payment Request #PR-000315. |
| Who raised it, and when | The requester’s name and the request date. |
| The total | Shown for payment requests and advances. A requisition is not priced, so it carries no total. |
| Each line | The purpose or description, the amount, and its status. |
| Beneficiary details | Name and bank in full — the account number is cut to its last four digits. |
| A footer line | States plainly that the view is read-only, when the link expires, and that account numbers are partially hidden. |
What it deliberately leaves out
Attachments, the conversation, the note to approvers, the project, the approval stage, and the retirement figures on an advance are not on the public page. Neither are any internal identifiers or email addresses. A recipient can read the request; they cannot comment, approve, or act on it.
When a link stops working
| Status | Meaning |
|---|---|
| This link is no longer available | The address is unknown, has expired, or was replaced by a newer link. All three read the same on purpose — the page never confirms whether a request exists behind an address that is not valid. |
The recipient is told to ask you for a new one. Creating another public link is all that is needed.
The record
Creating a public link is logged: it appears on your business's activity trail as a link created for that request, and is recorded as a data export for security review. Sharing a request is a deliberate, attributable act, not a silent one.
Related
- The request page — where Share lives
- Approve a request — for recipients who do need to act
- Spend — the whole module