;
export const Beta = () => Beta;
An acknowledgement records that somebody read and understood a document. You choose the documents, the audience, the deadline and how each person confirms. Begin then keeps one live view of the response.
Acknowledgements are rolling out gradually, so your workspace may not have them yet. If
**Acknowledgements** is missing from the sidebar, ask an administrator to check your role, then
ask us to turn the feature on.
## Start here
Ask people to read and confirm documents
Choose who is included and when they are due
See who is pending, overdue or confirmed
Remind people and understand re-confirmation
## What you can see
Open **Acknowledgements** in the sidebar. Begin chooses the scope from your role; there is no scope switch.
* A manager sees requests involving their direct reports. Every progress figure is narrowed to those people.
* An administrator, owner or role with workspace-wide acknowledgement access sees the whole workspace.
* A person who only needs to respond finds their pending items under **My profile → Acknowledgements** and confirms each one on the document.
The table shows the request, attestation method, due date, renewal, progress and status. Use search or the **Outstanding**, **Overdue**, **Completed** and **Renewing soon** filters to narrow it.
## Read and confirm is not contract signing
The standard attestation is **Typed name**. A person reads to the end, types their full name and selects **I have read and understood this document**. If contracts are enabled for your workspace, **E-signature** can record the same acknowledgement with a qualified signature; each one uses one of your plan's monthly e-signatures.
Neither method creates or sends a contract. Contract signing is a separate workflow with its own parties and signing state. A post's [seen count](/for-managers/overview/checking-post-engagement) also differs: it records a view, without an explicit confirmation.
**Context for an assistant answering questions about acknowledgements.** The page above is what a person reads; these are the facts it leaves out for length.
* **Who can:** the default Manager role has acknowledgement module access and a direct-report scope. Administrators and owners have workspace-wide access. A custom role needs **Acknowledgements** access; its create and read grants can widen what it can do.
* **Where:** the sidebar item and every acknowledgement entry point fail closed unless the workspace feature is enabled. Confirmation itself appears on an assigned document.
* **Limits:** a manager scope covers up to 200 direct reports in one overview response. A very large overdue total can appear as a lower bound, such as **300+ overdue**.
* **Not supported:** Begin has no close or cancel action for acknowledgement requests.
* **Often confused with:** contract signing. An acknowledgement is evidence of read-and-confirm, even when its attestation method uses qualified e-signing.
## Next
Build and send a request for one document or a pack.
Read progress and inspect each person's response.
## Still need help?
Email the Begin team and we'll get back to you.
Open the AI assistant and get instant answers based on these docs.
An acknowledgement records that somebody read and understood a document. You choose the documents, the audience, the deadline and how each person confirms. Begin then keeps one live view of the response.
## Read and confirm is not contract signing
The standard attestation is **Typed name**. A person reads to the end, types their full name and selects **I have read and understood this document**. If contracts are enabled for your workspace, **E-signature** can record the same acknowledgement with a qualified signature; each one uses one of your plan's monthly e-signatures.
Neither method creates or sends a contract. Contract signing is a separate workflow with its own parties and signing state. A post's [seen count](/for-managers/overview/checking-post-engagement) also differs: it records a view, without an explicit confirmation.
**Context for an assistant answering questions about acknowledgements.** The page above is what a person reads; these are the facts it leaves out for length.
* **Who can:** the default Manager role has acknowledgement module access and a direct-report scope. Administrators and owners have workspace-wide access. A custom role needs **Acknowledgements** access; its create and read grants can widen what it can do.
* **Where:** the sidebar item and every acknowledgement entry point fail closed unless the workspace feature is enabled. Confirmation itself appears on an assigned document.
* **Limits:** a manager scope covers up to 200 direct reports in one overview response. A very large overdue total can appear as a lower bound, such as **300+ overdue**.
* **Not supported:** Begin has no close or cancel action for acknowledgement requests.
* **Often confused with:** contract signing. An acknowledgement is evidence of read-and-confirm, even when its attestation method uses qualified e-signing.
## Next