What you'll achieve
You will configure shared task boards and sprints, maintain report templates, and govern disclosure and verification settings as a coherent organisation service.
Who this is for
This guide is for an Organisation Administrator with the permission or assigned action described below. If the navigation or action is missing, check the selected organisation, effective account level, feature state and role before assuming the product is unavailable.
Before you start
Check that you have:
- Agreed task states and sprint cadence.
- Approved reporting templates and data owners.
- A disclosure audience and evidence-sharing decision.
- The authority and evidence needed for organisation verification.
1. Configure task-board columns
Open Tasks and choose the board context. Keep protected columns intact, add only states people can distinguish, and order them to match the real flow of work.
2. Configure sprints
Open Sprints. Create organisation-wide sprints with clear dates and purpose. Start and complete them deliberately; do not delete an active sprint to tidy the list.
3. Maintain reporting templates
Open Reporting. Start from a Backstory template or duplicate one into Your Templates. Check placeholders, headings and disclosure scope before using it for an export.
4. Review export history
Use Export History to confirm the intended template and operation. An export is a new information asset; store and share it under your organisation's controls.
5. Configure disclosure
Open Settings > Organisation > Disclosure. The Disclosure control plane sets the maximum Level for each evidence type and audience. Select the relevant matrix cell, review its allowed level and save the approved ceiling. Live or Snapshot is chosen when evidence is attached, not in this matrix. Restore Backstory baselines resets all organisation ceilings after confirmation; existing object restrictions can remain tighter.
6. Verify your organisation's domain
Open Verification and start the domain-verification flow. Enter the domain your organisation controls. Give the displayed TXT name and value to the person responsible for DNS; after they add it, return and verify. Check Verification history for the result. DNS changes can take time to appear. This verifies domain control, not a certification of the organisation's compliance.
Check it worked
- Board columns and sprints match the agreed working method.
- Report templates render the intended fields without exposing unnecessary data.
- Disclosure settings match the named audience and purpose.
- Verification history reflects the actual request and decision state.
If something goes wrong
| What you see | What to do |
|---|---|
| A protected task column cannot be edited | Keep it and adjust the surrounding configurable states. |
| A report export contains too much | Stop distribution, restrict the template and handle the exported copy under your incident or correction process. |
| A disclosure audience is ambiguous | Do not publish. Resolve who the recipients are and what they may see. |
| Verification is pending | Describe it as pending; do not present the organisation as verified. |
Human judgement, security and privacy
Configuration turns organisational choices into defaults. Defaults help consistency, but they do not remove the need to review a specific report, disclosure or verification claim.
What's next
Run a quarterly configuration review with task, reporting, privacy and supplier-profile owners.
Need help?
Use your organisation's approved Backstory support route. Include the organisation, page and action that failed, but do not include passwords, invitation links, secret keys or unnecessary personal or confidential content.