Skip to content
Content SnareHelp centre

Client access and security settings

Quick answer

By default, your client opens a request from a private link with no login, and sets their own PIN the first time. To make them sign in, turn off Allow access without logging in on the request. Changing the account-wide defaults only affects requests you send from then on.

How clients open a request by default

By default, your client opens a request from a private link, without an account or a login, and sets their own PIN the first time they open it. So getting in normally takes two things, a link and a PIN, and you only need to change anything if you want it tighter or more relaxed.

The link (plus the PIN if you keep it on) is how your client gets in, so treat the link like a key. It works for anyone who has it, which matters most when a client forwards the request email to someone else or somebody else reaches their inbox. Require a login when the answers are sensitive enough that a forwarded link would be a problem. Once you have what you need, archive the request to end the client's access. If your account lets clients download a completed request, marking it complete leaves that download link working, so see can clients view or download a completed request before you rely on completing it.

If you want the fuller picture on how your data is protected, see how secure is my data.

Ways to control access

You have a few ways to control how clients get in and what they can see, from the default link through to a full login.

Option What it does When to use it
Shareable link Your client opens the request from a link, with no account and no login. This is the default. Everyday requests where you want the fewest steps for the client.
PIN code Adds a short code your client sets the first time they open the request. A light extra check when the information is a little sensitive.
Require a login Your client has to sign in before they can open the request. The most protection, for sensitive work where a sign-in step is worth it.
Magic links Lets clients sign in with an emailed link instead of a password. When you require a login and want clients to sign in without a password.
Confidential answers Hides an answer once the client submits it, until someone reviewing the request unlocks it. Protecting single answers, like an ID number, on an otherwise open request.
Close access after the due date Ends your client's access to the request on its due date. When your client has a hard deadline.

A request is either a shareable link or a login. A client who signs in to their Content Snare account can still open a shareable-link request that way, and isn't asked for the PIN. Turning off Allow access without logging in switches that request to a login, so your client will not see a PIN prompt and a sign-in screen on the same request.

To close access on the due date, turn on Close client access after the due date on the Publish step of the request builder, the quick request publish screen, or the Finalize step of a recurring request. It is off by default. Access ends on the due date at the time of day you published the request, in your organization's time zone. Expect it within about 15 minutes of that time. The request then shows as Expired and your client's link stops working. An Administrator sets the time zone: click your avatar in the top right, choose Settings, then Company > Language and Regional > Time Zone.

Where to find these settings

To open any of these, click your avatar in the top right, choose Settings, then pick the section you need. The account-wide defaults for new requests sit on Request Settings. That is where you set Enable access without login by default and Protect requests with a pin code by default. Magic links and two-factor authentication for your team are on Security & Access.

Only an Administrator can change these account-wide defaults.

Add a PIN code

The first time your client opens a request that has a PIN, they choose the code themselves. You cannot set it for them. After that, the same code opens every PIN-protected request they have with you.

To turn a PIN on for one request:

  1. Open Requests.
  2. Open the request.
  3. Choose Client access settings from the actions along the top.
  4. Turn on Allow access without logging in if it isn't already. The PIN setting sits under it and stays grayed out until it's on.
  5. Turn on Protect with a pin code.

To add one to every new request instead, turn on Protect requests with a pin code by default in Request Settings. For how clients set and reset their code, see how PIN codes work.

Require a login

To make clients sign in, turn off Allow access without logging in on the request. That switches the request from a shareable link to a login, and the client opens it through their Content Snare account instead.

Clients can sign in without a password using a magic link, a one-time link that is emailed to them and lasts a short while. You turn magic links on or off for the whole account with Enable Magic Links on the Security & Access page, and they start switched on. If you turn magic links off, any that are already in clients' inboxes stop working the next time a client clicks one. A client who has never set a password will then need to use Forgot password to get in. See magic links for how they are sent and how long they last.

Hide individual answers

Mark a single question's answer as confidential and your client can no longer see it once they submit it. Someone reviewing the request enters their own password to read it. This works per answer, not per request, so you can keep one bank detail private while the rest of the request stays open. You can use it on the common text, number and file question types.

Use it sparingly, only on the answers that need it. Your client cannot go back and check anything they have submitted confidentially, so a request full of confidential questions is harder for them to work through. See confidential fields for which question types support it, who can unlock an answer, and how the client experience changes.

Change a setting after you have sent a request

Changing the account-wide defaults only affects the requests you send from then on. Requests already out with your clients do not change. To protect a request that is already gone, turn the PIN on for that one request. It takes effect immediately, even on the link your client already has. You set this on the request, so on a request with more than one client it changes how all of them get in. Adding several clients to a request doesn't split it into one request each. They work on the same request and can see each other's answers.