Some of your work needs an answer from somebody who does not work with you: a supplier confirming a delivery date, a client approving copy, a contractor filling in hours. An update request is how you get that answer without emailing a spreadsheet back and forth and without giving anyone an account.
You choose the tasks, you choose the fields, and you choose whether each field is hidden, readable or editable. They see that and nothing else.
The update request wizard Board, Create update request
1
Creating one
Two short steps and a review.
1
Start it from what you want to share
Right-click a board, a group or a task and choose Create update request. What you started from becomes the scope, and the scope is fixed once the link exists: to share something else, make another link.
2
Step one: decide what each column shows
Every column on the board is listed with three choices: Hidden, View or Edit. Hide all, View all and Edit all set the lot in one click, then adjust the ones that matter. The task name is always visible, and the created and updated stamps stay read-only.
3
Step two: expiry, recipients and notifications
Name the link so you recognise it later, set how long it lives, add the people who may open it, and choose who gets told when something comes back.
4
Review, then send
The last step shows exactly what the recipient will receive. Send it and each person gets their own invitation email.
Watch out for letting somebody edit a People column. That would let an outsider reassign your task, so Gript warns you when you do it.
2
Who can open it
A forwarded link does not let a stranger in.
You add recipients by name and email address, and that list is the lock. Only those addresses can open the link, and there is no password to invent, share or reset.
1
They reach a page titled Sign in to view tasks
It shows the name of the link and the board, so they know what they are opening.
2
They type their email and press Send me a code
A six digit code is emailed only if that address is on your recipient list, so a forwarded link does not let a stranger in.
3
They type the code and press Verify and continue
Codes last ten minutes.
4
If it goes wrong
Resend code sends another, and Change email goes back a step.
SettingWhat it means
One-time useSealed the moment they submit. Right for a single confirmation you do not want revisited.
Expires after N daysAnything from 1 to 365 days, counted from when you save. The link closes itself when the time is up.
PermanentNever expires. Useful for a standing supplier relationship, but review these now and then.
Notifications are set here too: tell the task assignees when something is submitted, and tell you when the link is opened or submitted.
4
What the outside person sees
On their pageWhat they get
What is listedOnly the tasks you shared, with only the columns you allowed.
Editable fieldsTyped straight into, saving as they go. There is no giant Submit button to miss.
View-only fieldsShown, but greyed.
Hidden fieldsNot there at all, not even as an empty column.
What you get backTheir changes write straight onto your board, attributed to them by name, so the task history shows who did what.
Whatever they change writes straight onto your board, attributed to them by name, so the task history shows who did what.
Each shared task also carries a small message button, which is the other half of this feature. See Client messages.
5
Keeping track of your links
Open The Hub from the grid icon in the top bar and switch to Update Requests. Every link you have made is listed, grouped by board, with its scope, its recipients, its expiry and its activity.
The audit trail
Every step is recorded: link created, portal opened, recipient signed in, each field change from old value to new, submitted, invitation resent, revoked or expired.
Editing a link
Change the column permissions, the expiry, or the recipients. Adding a recipient sends them their own invitation. The scope cannot be changed.
Resending
Resend the invitation to one recipient without touching anyone else.
Revoking
Cuts access off immediately and tells the recipients. Use it the moment a project ends.
On the board itself, a task that a recipient has edited shows a small unseen-updates dot on its row, so you notice the answer without going looking for it.
Do they need a Gript account?
No, and they cannot get one from this link. They sign in with a one-time code sent to the address you listed, and they only ever reach the tasks and fields you chose.
Can I share a whole board this way?
Yes. Start the update request from the board rather than from a task and the scope is the board. You still control every column, so a whole board can be shared as read-only with two fields open.
What if I need to share different things with two clients?
Make two links. Each one has its own scope, its own recipients, its own permissions and its own conversation, and neither client ever learns the other exists.
They say the code never arrived.
Check the address is exactly the one on the recipient list, ask them to look in spam, and use Resend code. If the address is wrong, edit the link and add the right one.
Is this the same as sharing a board publicly?
No. A public board share is a read-only page anyone with the link can look at. An update request is named people, signing in, editing specific fields, with an audit trail.
