Understanding Gatheroo’s terminology makes it easier to follow guides, configure settings, and communicate with your team about how the platform works. Here are the key terms used throughout Gatheroo.
People
- Account Owner
- The person who created and owns the Gatheroo subscription. There is one Account Owner per account. They have full access to all settings, billing, and data.
- Team Member
- Anyone added to the Gatheroo account by the Account Owner. Team members log in with their own credentials and have access based on their assigned role (Admin or Member).
- Admin
- A team member role with broad access – including Global Settings and domain verification – but not billing.
- Member
- A team member role with access to day-to-day work (requests, contacts) but not account-wide settings.
- Client / End Client
- The person or business your team sends requests to. Clients do not have a Gatheroo login – they access their request via a secure link sent to their email.
- Contact
- A client’s record stored in Gatheroo, containing their name, email, and optionally their company. Contacts are who you address requests to. Once attached to a request, they are referred to as Recipients.
Requests
- Request
- The main unit of work in Gatheroo. A request is a form built by a team member and sent to a client to collect information or documents.
- Draft
- A request that has been created but not yet published or sent.
- Published
- A request that is ready to send but hasn’t been sent yet.
- Sent
- A request that has been sent to at least one client.
- Completed
- A request where the client has submitted all required responses.
- Archived
- A request removed from the active view but kept on record. Archived requests don’t count toward your plan’s active request limit.
Draft, Published, Sent and Completed requests count towards your Active Requests. Archived requests do not.
Request structure
- Welcome Message
- An introductory message shown to the client at the top of the first page of a request. Set in the Request Builder.
- The top level of a request’s structure. A request can have multiple pages, presented to the client one at a time (like chapters in a document).
- Section
- A grouping of fields within a page. Sections help organise related fields together and can be labelled with a heading.
- Field
- An individual question or input: for example, a text box, file upload, date picker or signature. Fields are the building blocks of a request.
Page
If a request has only one page or section, these will only appear when a second is added.
Templates
- Template
- A saved request structure that can be reused to create new requests quickly, without rebuilding from scratch each time.
- Template Library
- A collection of pre-built request templates provided by Gatheroo, organised by industry and use case. You can add them to your account with one click.