Skip to content
Content SnareHelp centre

Glossary

Quick answer

In Content Snare, a request is a private online form you send a client to collect their documents, files and answers. A request is made up of pages, and each page is divided into sections of questions, called fields. A reminder schedule and a communication schedule are the same thing.

Terms are in alphabetical order, and each links to the article that explains it in full.

Active request. A published request. Your plan limits how many you can have published at once. Complete or archive a request to free a slot; at the limit you can't publish another until you do. See request statuses and what to do at the limit.

Client. The person you send a request to, whether or not they're a "client" in the everyday sense of the word. Adding a client doesn't use a team-member seat. See clients.

Communication schedule. Another name for a reminder schedule. See the entry below.

Confidential field. A field whose answer is hidden once your client submits it, so it can't be read again from the request. To see one, a team member with the right access enters their own password to unlock it. It's only available on some field types. See confidential fields.

Credit. One word that covers two separate meters. You spend a verification credit when you run an identity or AML check. SMS credits are the monthly text-message allowance that comes with your plan; they don't roll over, so if you run out, texts pause until your next monthly reset while the rest of your account carries on. See verification credits and plans and limits.

Field. A single question your client answers. Content Snare's own screens mostly call it a field, and question is the everyday word for the same thing. The field type sets what kind of answer it collects, from text and uploaded files to ratings, signatures and identity checks. See field types.

Internal field. A question only your team can see. Clients never see it, and you can exclude it from exports. Use internal fields for notes, checklists, files and review outcomes. See internal fields.

Page. The top level of a request's structure. A request is made up of pages, and each page usually covers one broad area, like contact details or compliance. A page is divided into sections. See what's in a request.

Reminder schedule. The shared set of automated emails and text messages Content Snare sends about a request. Most of them chase a client for what they still owe you, and some go to the request owner instead, like a note that an answer is waiting for approval. The app also calls this a communication schedule. The screen where you build one is headed "Reminder Schedule Details", and the picker where you attach one to a request says "Select a communications schedule". They're the same thing. See reminder schedules.

Request. A private online form you send to a client to collect their documents, files and answers. Each client you send it to gets their own link, and they can't open the request until you publish it. See what's in a request.

Request owner. The one team member assigned to a request. The owner gets the notifications about it, so a client's comment notifications go to them and not to the whole team. The four team roles are Administrator, Editor, Reviewer and Viewer, and owner is a separate assignment on top of whichever role someone holds.

Section. A group of questions inside a page. Sections divide a page into smaller sets, each holding the questions your client answers. See what's in a request.

Team member. A person in your account who holds one of four roles: Administrator, Editor, Reviewer or Viewer. New members start as Editor, and each one counts against your plan's team-member limit. You'll see them called users or team members, and both mean the same thing. See team members and permissions.

Template. A saved request, page or section you can reuse across clients, so you're not rebuilding the same thing every time. See templates.