Proposals, and what never goes through an assistant

For some kinds of change, saying yes in the chat is not enough. Your organisation's policy decides which.

Proposals

When a change needs approval, confirming it in the chat makes a proposal instead of the change itself. Nothing changes yet.

• A colleague approves or rejects it in EstatesBase, on the Approvals page. They are told it is waiting.
• The approver is a Site Manager or above. It is never you, and never a trustee.
• A proposal waits for up to 7 days. If nobody decides it by then, it expires and nothing changes.
• When it is approved, the change is made exactly as previewed and recorded under your name, with the approver's name beside it.

Changes to how your organisation is set up, and anything touching people, safety, money or a legal duty, are always proposals. They are never made from the chat alone.

What never goes through an assistant

Some things stay a person's own act in EstatesBase, whatever the policy says:

• deleting anything
• changing anyone's access: roles, sites, groups, or inviting someone
• passwords, two factor sign in and sign in settings
• the AI assistants settings, connections and approvals themselves
• Board and sign off decisions, declarations and attestations, and going live

If you ask for one of these, the assistant should tell you it cannot, and EstatesBase refuses it. Do it yourself in EstatesBase.

Check your understanding

You confirm a change in the chat and the assistant says it has been sent for approval. What has happened?

• The change has been made and will be checked later
• Nothing has changed yet: a colleague decides it in EstatesBase within 7 days
• You need to approve it yourself on the Approvals page

Which of these can never be done through an assistant?

• Raising a request for a broken window
• Changing a colleague's role
• Asking which compliance tasks are overdue