Glossary of terms
This document lays out the specific usage of some terms within Zivver products and documentation.
a code which is communicated to a recipient by means other than SMS or mail, and which is used to access Zivver messages addressed to said recipient.
the process of granting an rights to send and receive Zivver messages via another account. User and functional accounts can be delegated.
account which is granted Zivver administrator rights.
an email address which automatically forwards received Zivver messages to the primary email address. An alias can not send a Zivver message.
code to be used to restore access to your account in the event that you lost access to your 2FA.
filtering rules for Zivver message drafts.
see functional account.
a domain name which has been claimed by a Zivver admin.
messages between Zivver users which share a topic and a recipient list.
a web widget which directs guests to the Zivver WebApp so they can compose a Zivver message to a Zivver user.
a user account which is allowed to read, send and receive email using the address of another account.
a user account for which a delegate exists
a recipient email address which doesn’t belong to a claimed domain
extra identity check
extra login method
second authentication factor in a 2FA scheme
user account which is not managed by an organization administrator and is not in a claimed domain. also known as unmanaged account
an account which is used by multiple members of an organization, such as
a type of Zivver account which can only be used to send messages to other Zivver accounts and is limited in other ways. all guest accounts are free accounts
an explanatory message which can be sent (depending on admin choice) to recipients of Zivver messages which have never received Zivver messages before.
email which is sent to addresses to join an organisation and create an account if there isn’t an existing account for the email address invited.
a user account which is managed by a Zivver administrator.
see user account
an email message which notifies a recipient that a Zivver message has been sent to them
see: managed account
organization access code
an access code which is available to all senders within an organisation.
organization address book
contacts in a Zivver address book which are shared between members of an organization
open conversation starter
a conversation starter type which allows anyone, regardless of whether they have a Zivver account, to start a Zivver conversation with any (specified) contact within your organization.
contacts within your own organization.
personal access code
an access code which is not shared with other Zivver users within the sender’s organization; compare: organization access code
see: free account
contacts added to the address book by yourself.
personal conversation starter
a conversation starter which allows anyone without a Zivver account to start a Zivver conversation with a specific contact within your organization.
personalized conversation starter
a conversation starter which has been branded or otherwise customized for a certain organization
person that receives a Zivver message
a code used to restore access to messages after a password change
free accounts in a claimed domain. Accounts in claimed domains are normally all managed.
shared access code
shared address book
an address book which contains members of various organizations. Users can apply for inclusion in a shared address book.
a recipient address which features in a shared address book
recipient identity verification by means of an SMS sent to a known mobile phone number
see free account
a Zivver account which does not have administrator privileges; guest accounts are also user accounts
a one-time access code that is sent via email
email containing an access code
a method to verify a recipient’s identity prior to granting access to a Zivver message. Zivver uses access codes for this purpose.
a list of verification methods used for various recipients.
credentials which authenticate a user for an SSO solution used by an organization, such as AD FS; proof of identity obtained from such a system can be used to login to Zivver, provided the required integration is already set up
username/password pair used to log in directly to a Zivver account; compare: workplace credentials