Security
Each client sees its own tickets. Your ClickUp stays yours.
How TickFlow Web keeps your clients apart, signs people in, guards your ClickUp token, and limits what the browser extension and the feedback widget can see and send. Only what the product does today.
Clients kept apart
One list for your team. A locked view for each client.
The server decides what a person can see from who they are, never from what the page asks for. Switch who is signed in, then try to peek at another client.
ClickUp · one shared support list
- Checkout button does nothing on Safariacme-dental
- Invoice PDF shows the wrong logoglobex
- Booking form e-mails go to spamacme-dental
- Add a second admin for the Montréal officeglobex
- Staff page photos are blurryinitech
Dana’s portal · Acme Dental
- Checkout button does nothing on Safari
- Booking form e-mails go to spam
- Your organisation, your subdomain
- Each organisation signs in on its own address. A reserved name such as portal can never be claimed.
- A client account, a tag
- Every ticket carries its client’s tag. A client’s people are shown only the tickets with their account’s tag.
- Asked, and refused
- Ask the API for another account’s tickets and it answers 403. Your own team can open any client, after a check that the client is yours.
- Roles that mean something
- Organisation admins connect ClickUp and brand the portal. Client admins manage their own people. Client users file and follow tickets.
Sign-in
No passwords to steal. Links that do not last.
Everyone signs in with a link e-mailed to them. It expires after 15 minutes, and asking for a new one retires the old one. Blocked people and organisations are refused. Try it.
northwind.tickflow.co/login
dana@acme-dental.example
If this email is registered, a sign-in link has been sent to your inbox.
Exactly the same reply for an address that is not registered, so the form cannot be used to find out who has an account.
Dana’s inbox
- Sign in to Northwind Studioexpires in 15:00
Client admins can share a join link for their account, and revoke it when it has done its job.
Your ClickUp token
Encrypted at rest. Never sent back.
The API token you connect is encrypted before it is stored. Every settings response shows it masked, and the connection test reports which check failed without ever returning the token. Your clients never get a ClickUp login of any kind.
// GET /clickup/settings
{
"clickupApiToken": "********",
"clickupListId": "901…"
}
// at rest
enc:v1:<iv>:<tag>:<ciphertext>The browser extension
It sees a page only when someone asks it to.
Every permission it asks the browser for, and why.
- activeTab + scripting
- The reporter is put on a page only after the person clicks the extension’s icon there. No access to every site you visit.
- tabs
- Takes the screenshot of the visible tab, finds the tab to report from, and opens your portal.
- storage
- Keeps the person signed in and remembers where they left the floating button.
- Hosts
- Its own pages only: tickflow.co and its subdomains. It does not ask for <all_urls>.
- Remote code
- None. All of its code ships in the package; answers from the API are read as data, never run.
The feedback widget
Open to the public. Closed to everything else.
The widget takes reports from anyone on your client’s site, so it gets the strictest rules: where it works, how much it accepts, what it sends and what it gives back.
Only the sites you list
Each widget key works only from the site addresses you allowed for it, and needs the key itself. Localhost and loopback addresses are refused.
Limits per visitor and per key
Rate limits on every widget request, so a script cannot flood your list.
Scrubbed at capture
Tokens and keys in URLs, JWTs and e-mail addresses are removed before anything is stored or sent.
Only a reference back
The anonymous reporter gets a reference such as TF-8F42-QK. Never the ClickUp task id or a link into your workspace.
Shown before it is sent
Page, browser and recent errors are listed in the panel; the reporter can switch them off.
One outage, one task
Identical reports from one client within 30 minutes add up on the first task instead of opening more.
Your data
Where it lives, and what we keep.
Tickets live in your ClickUp
Tickets, comments and attachments are ClickUp tasks in your workspace. The portal reads and writes them through ClickUp’s API, only in the one list you chose.
Files pass through
Uploads go to the ClickUp task. Your organisation sets which file types are allowed and how large they may be; the API enforces it.
What TickFlow keeps
Your organisation, client accounts, people, branding and settings. Logos are stored privately and shown through links that expire.
Sign-in kept out of the logs
Sign-in requests are recorded in the activity log without their bodies, so a sign-in link never lands there.
Questions from your security team? Write to hello@tickflow.co. Read the privacy policy and the terms of service.
Safe for your clients. Simple for your team.
Start free. Connect ClickUp, pick your support list, brand your portal and invite your first client.
Questions first? Write to hello@tickflow.co or read the FAQ.