Product documentation
Understand data access behavior
What you can see or query can differ from another user even when both use the same DataFact workspace. Availability can depend on your corresponding access, the database connection account, and policies applied to the dataset.
User-visible effects
Access can affect:
- whether the Datasets area or a specific dataset is visible;
- whether create, edit, delete, or knowledge controls are available;
- which source schemas and tables the database connection reports; and
- which rows a query can return.
A successful database connection test confirms connectivity; it does not prove that every user will receive the same tables or rows.
If data is missing
- Confirm that you opened the intended workspace and dataset.
- Check the dataset's database connection and selected schemas in Project Description.
- Compare the question and filters with the source scope.
- Record the dataset name, session, approximate time, and the expected versus observed result.
- Ask the dataset owner or your support contact to verify access outside this guide.
Do not work around a missing-data result by switching to an unrelated dataset or by assuming that an empty result means the source contains no matching rows.
Scope of this guide
This page explains observable behavior only. It does not document access-policy, identity, credential, or row-filter configuration.