View first
Review records by default. Editing should be an explicit, scoped action.
Clear boundaries matter
Review the product’s operating principles and ask how access, data and support are handled in the specific deployment you are considering.
Operational principles
The product's governance materials emphasize deliberate changes, role-aware access and historical record preservation. Confirm the exact controls and responsibilities for the environment being evaluated.
Review records by default. Editing should be an explicit, scoped action.
Confirm which roles can access each workflow and how protected operations are enforced.
Financial and academic records need clear handling rules for historical information.
Discuss hosting, provider access, backup, recovery, retention, export and support terms.
Questions worth asking
A screen or setting alone does not establish a connected provider, legal compliance, certification or a service guarantee.
Review role definitions, administrative access, support access and the approval process for sensitive work.
Confirm who makes backups, where they are held, how restores are tested and which service terms apply.
Agree retention, export, deletion, incident response and support responsibilities for the selected deployment.
Verify the provider or device, configuration, permissions and test environment. Delivery is not implied by a product screen.
Make the conversation specific
Request a walkthrough and include the operating questions your team wants to resolve. Do not send sensitive records.