Use the selected SmartFACT Data site when investigating access or service readiness. Owner can inspect Team & access and Health & recovery. The working roles for ordinary tables, SKU templates, sources and shops remain separate, so an administrative screen is not evidence that every task is available to that person.
Check central and site access together
Open Team & access. SmartFACT Accounts shows the person's central product roles and provides Manage your organisation and SmartFACT Data roles in Accounts. Use that source to arrange organisation membership and explicit product grants. A local site assignment cannot widen those central grants.
In People at this site, compare the effective SmartFACT Data roles with Access source. Follows Accounts and Restricted at this site have different meanings. A saved restriction can remain narrower than a later central grant. Removed or waiting identifies people without normal current site access; seeing their name is not evidence they can work here.
If the central role is correct but the site remains restricted or removed, ask the responsible administrator to resolve the actual assignment. This deployed Team screen presents those facts and the Accounts link; it does not offer a local role-editing form to bypass a restriction. Do not share another person's sign-in.
Check Roles and actions for template-specific table authority, Operator shop read/replay versus Supervisor deduction decisions, and the extra reader grant an Author needs for the visible saved-selection preparation page.
Read the right kind of health warning
Health and recovery separates Installation checks from Backup and service readiness. Installation status concerns whether the service can record changes. The separate readiness warnings can still identify work required before customer production even when a page opens normally.
This workspace shows attention counts for the selected workspace. An external source can be both overdue and have a failed refresh. Native reference tables do not become stale merely because nobody has edited them recently. Follow the relevant source, feed or connection record rather than treating every attention count as the same failure.
Use External sheets, Source observations and History, export and recovery for their specific freshness and restore boundaries. A healthy installation does not clear individual held deliveries or restore old observations' age.
Download the diagnostic without sending customer data
An Owner uses Download a support diagnostic. Choose Activity totals, using No history or an offered recent period, then Download diagnostic. Complete the requested recent identity verification through Accounts. Confirm the downloaded file was prepared rather than assuming a successful-looking page means a file was saved.
The diagnostic contains build and package versions, check codes, workspace counts and optional daily totals. It excludes source rows, sheet identifiers, names, connection keys and customer data. It is downloaded locally and is not sent to support automatically. Review the file before choosing to share it.
A refused or unrecognisable diagnostic answer is not a reason to alter source data. Check the actual sign-in, service and current page state, preserve the visible problem and use the appropriate support process. A diagnostic file does not establish production service or customer task qualification.