Skip to content
shuffl
Get started

Searches the public product guides only. Nothing from a workspace is read, and questions are not saved.

How-to guide

Access requests

Ask for the tools you need from one catalog. Approvers decide with a tap in Slack or email, owners set it up, and you hear either way.

For Everyone using Shuffl

On this page

App links open your signed-in workspace. Check the selected workspace before making changes.

Ask for an app

Open Apps from the menu, or ask Mello for access to a tool by name. Each card says what the app is for and who approves it. Pick a level when the app has them, say what you need it for, and send.

Open apps grant at once. The rest go to the approvers: your manager, named people or a group, as the app is set up. A request waits a week by default, then expires and you are told. Your requests sit on your Me page.

If the catalog is empty, Ask HR for an app sends HR the name of the tool you need, with the same review as any HR request.

The Apps page: a grid of cards for Figma, GitHub, HubSpot, NetSuite and Notion, each with its initial, a line on what it is for, its owners, how requests are decided and a Request access button. Notion shows Granted.
Every app people can ask for, with who approves it on the card.
The Request GitHub dialog: a line saying who approves, an Access level choice showing Member, a box for what you need it for, and Cancel and Request access buttons.
Say what you need it for; the approver reads it on their card.

Approve and set up access

Approvers get a card in Slack or by email with who asked, for what and why. Approve with one tap; Decline asks for the reason the person sees. The first approver to answer decides; the others see it was handled. Nobody approves their own request.

Approved requests go to the app’s owners to set up, unless the level is mapped to a group (below). Once the person has access, Mark as done tells them. Owners can also remove access later, and the person hears why.

The Approvals tab and the Requests notification setting show only to people who decide requests: owners, named approvers, their groups, managers an app asks, and administrators.

Access request to approveThe approvers an app names, each privately · When someone asks for an app that needs approval

ShufflAPP

Access request
Priya Natarajan asked for Figma (Editor).
AppFigma (Editor)
ForPriya Natarajan
DetailsJoining the design reviews for the onboarding flow.
ApproveDeclineAsk for more
Open in Shuffl
Waits 7 days for a decision, then expires. Priya Natarajan is told either way.
Access approvedThe person who asked, privately · When an approver decides on their request

ShufflAPP

Access request
Dana Okafor approved your access to Figma (Editor). The app owner is setting it up and you will hear when it is ready.
Your requests
The Approvals tab: under To decide, cards for Diego Ramírez asking for GitHub (Admin) and Olivia Brooks asking for Figma, each with why, how long it waits and Approve and Decline buttons; under To set up, Olivia’s approved HubSpot request with a Mark as done button.
Approvers and owners see what waits on them, on one page and in Slack.

Ask for anything else

Not everything is an app. On your Me page, New request asks for anything that needs a yes: a desk, a letter, a conference ticket. Say what you need; Mello picks the kind from your catalog and asks its questions. The kind says who decides.

Approvers find every request waiting on them in Approvals, the Inbox and Slack Home, and get the same card in Slack or email. Ask for more sends the person a question; their answer comes back on the card. Each request lists its history.

A request says in one sentence when the approver usually answers and when it closes if nobody does. Past that date it says Overdue and offers Ask HR. Your requests on Me lists questions for HR too, and Home shows the ones still waiting.

Request to approveEach approver in the request’s current step, privately · When someone asks for something their manager or a named person approves

ShufflAPP

Equipment request
Priya Natarajan asked for A second monitor.
ForPriya Natarajan
DetailsMy laptop screen is too small for the design reviews.
ApproveDeclineAsk for more
Open in Shuffl
Waits 7 days for a decision, then expires. Priya Natarajan is told either way.
Approver asks for moreThe person who asked, privately · When an approver presses Ask for more

ShufflAPP

Equipment request
Is this for the office or for home?
Dana Okafor needs a little more before deciding on A second monitor.
Reply
Open in Shuffl
Your reply goes to the approver, and the request waits for it.
The Approvals page: under To decide, Diego Ramírez asking for A standing desk (Equipment request) and Olivia Brooks asking to work from Lisbon for two weeks, waiting for her answer, each with the day it expires.
Every request that waits on you, whatever it asks for.
Olivia’s Lisbon request open: the note she wrote, Priya’s question about dates and core hours, who decides, the history with Asked and Asked for more, and Decline and Approve buttons with a … menu.
A request keeps its whole history: asked, questioned, answered, decided.

Keep the request catalog

Administrators keep the request catalog from Approvals. It starts with ten kinds, from new equipment to a new Slack channel, plus Something else for anything that fits none; those go to an administrator.

Each kind has its questions, who approves it, who carries it out and how soon it is answered. Describe a new kind in a few sentences and Draft with Mello fills in the form for you to check.

Mark a kind Named people only for sensitive asks: only the people you name see and decide those requests, not every administrator. A manager can file for a report, who is told.

The Request catalog: New equipment, Equipment repair, Expense approval, Employment letter, Time off and more, each with who approves it, how many questions it asks and how soon it is answered, Something else last, and an Add a type button.
Everything people can ask for, with who approves each.
The New equipment type open for editing: its name, what it is for, the kind Equipment request, and three questions, Item (required), What it’s for and Needed by, each with its answer type.
A type holds its questions, approvers and who carries it out.
The New request dialog: What you need says A second monitor, Kind shows New equipment with Mello picked this from what you wrote and Your manager decides, the Item question answered 27-inch monitor, and the details.
Mello picks the kind from what you write and asks its questions.

Let Shuffl do it in Slack

Some kinds Shuffl carries out itself in Slack once approved: create a channel, add the person to a channel or user group, or invite a guest. Approvers see exactly what will happen before they say yes.

Shuffl checks Slack shows the change before it calls the request done, and the receipt names the channel. If Slack refuses or does not answer, the request waits with the reason and Try again for whoever carries it out.

A public channel kind can skip approval; private channels and guests always wait for a yes. A done request can be taken back from its … menu, which archives the channel or removes the person, and the history keeps both.

If Slack has not granted what a kind needs, the catalog says Connect Slack to enable, or Reconnect once Slack is connected. People do not see it until you do that under Settings → Integrations.

A New Slack channel request open for its approver: channel name spring-catalog, Public, what it is for, and a box reading Once approved, Shuffl will create the public channel #spring-catalog and add Olivia Brooks, with Approve and Decline.
The approver sees exactly what Shuffl will do in Slack.
A New Slack channel request that did not go through: the box says A Slack channel with that name already exists, the history shows approved, started and failed, and the footer has Try again.
When Slack says no, the reason shows with Try again.

Take requests in a channel

Pick a Slack channel people already ask in, like #help, under Requests → Settings, and choose how Shuffl listens. Shuffl has to be in the channel; public channels can be joined from the same picker.

Always reads every new message. Mello answers in the thread when Knowledge covers it, and files a request when it does not. When asked does the same only when someone mentions @Shuffl. Silent files without answering and sends the receipt by direct message.

Anyone can file someone else’s message by reacting with :ticket:. A filed request gets one card in the thread that shows who it waits on and updates as it moves. Sensitive requests move to a direct message, so the channel only sees that they moved.

Request settings: #coffee-club takes requests, set to Always, with 2 filed and 3 answered by Mello in the last 30 days, and a picker to add another channel.
Each channel says what came in this month.

See which requests needed nobody

Culture → HR requests → All figures ends with Requests: how many were filed, the share resolved without a person, response and resolve times, and overdue ones, by week and kind.

Without a person means nobody but the asker decided or did anything: a letter issued by policy, or a channel post Mello answered from Knowledge. An approval by a person counts as a person. Counts under five read a few.

Download CSV saves the weekly table for a pilot report, with counts only. The Impact section on Culture and the weekly HR digest show requests without HR too.

The Requests section of the HR requests insights page: figures for requests filed, the share resolved without a person, time to first response, time to resolve and how many are past their target, a weekly chart of filed and resolved without a person, and a By kind table.
How many requests needed nobody, by week and kind.

Send proof of employment letters

Ask for a Proof of employment letter and Shuffl drafts it from People on your template: name, job title and department, start date and employment type. You pick what it says; it states nothing else.

A letter without a salary needs nobody and is ready to download in a minute, from the request and from the message you get. If People is missing a fact the letter states, it goes to an approver first.

In the catalog, administrators set the company, address, who signs and an extra paragraph, with Preview for a sample. Salary letters, when turned on, wait for an administrator, who types the figure. Shuffl never reads pay from your HR system.

Each letter carries a reference, so a landlord or bank can ask HR to confirm it. Only the person and whoever handles requests can open it.

Letter readyThe person who asked, privately · When a proof of employment letter is issued

ShufflAPP

Proof of employment letter
Your proof of employment letter is ready.
Download letterYour requests
Only you, and the people who handle requests here, can open it.
Salary letter to approveEach approver, privately · When someone asks for a letter with their salary

ShufflAPP

Proof of employment letter
Priya Natarajan asked for Proof of employment letter.
What it’s forA mortgage or loan
Include my salaryYes
ForPriya Natarajan
Approve in Shuffl
Approve it in Shuffl, where you add the salary figure. It never goes through chat. Waits 7 days for a decision, then expires. Priya Natarajan is told either way.
The Letter template dialog: company name Northwind Traders, its address, Signed by Priya Natarajan, an extra paragraph saying the letter does not guarantee future employment, and Let people ask for their salary switched on.
One template for every proof-of-employment letter.
A Proof of employment letter request for Diego Ramírez marked Done: what it is for, who it is addressed to, what it says, a box reading Diego’s letter is ready with a Download letter button, and the history.
The letter is ready to download from the request and the receipt.

Grant through groups

Connect JumpCloud, Google Workspace or Microsoft Entra ID under People → Sync, then map a level to its groups when you edit the app. An approval adds the person to those groups and reads the membership back. The request says granted through the group.

A write the provider refuses leaves the request Not granted with the reason, tells the owners, and Grant again retries it. One it took but has not confirmed reads Checking until Shuffl reads it back; it is never written twice.

Removing access, or a last day, takes the person out of the groups. Every 90 days owners get the list of holders.

The Edit GitHub dialog: under Access levels, the Admin level with an Engineering chip and a Grant through a Fixture SSO group selector, and the note that a mapped level is granted by Shuffl.
Map a level to a group and an approval adds the person to it.

Keep the catalog

Apps is a beta feature. An administrator turns it on for the workspace in Settings → Beta features.

Administrators add apps with Add app, or import them from a connected identity provider with Import; the names, logos and links come across. Each app has approvers, owners who set access up, levels such as Member and Admin, and how long a request waits.

An app can be open to everyone, need approval or be closed to requests. Archiving an app closes its open requests. Every request, decision, grant and removal is written to the audit log and reaches your webhooks.

The GitHub app page: how requests work (needs approval, approved by your manager or Priya, waits 7 days, owned by Priya, github.com), the Member and Admin levels, every request with its state, who has it, and Archive app.
Each app shows its approvers, owners, levels and who has it.

Was this guide helpful?