Rowgate terms
- Organization: the customer company. Data sources, profiles, people and audit records belong to an organization.
- Administrator: the role that sets everything up: data sources, profiles, people, audit and plan.
- Employee: the role that only connects the AI and queries what their profile allows.
- Data source: a database connected to Rowgate.
- Exposed table: a table the administrator turned on in the data source. Only exposed tables can be added to a profile.
- Access profile: what a group of people can query: allowed tables, hidden columns and row rules.
- Hidden column: a column the profile can’t see. The AI doesn’t receive its contents and can’t filter or sort by it.
- Row rule: a sentence that limits the records of a table, such as “show only records where region equals the person’s value”.
- Access data: each person’s values used in row rules, such as
regiao: Sul. - Connector: the Rowgate address each person adds to their AI assistant.
- Authorization: the permission a person gives, with their own account, for an assistant to query Rowgate on their behalf.
- Audit: the record of every AI query and every change in the panel.
Technical terms
- MCP (Model Context Protocol): an open standard AI assistants use to talk to external tools, such as Rowgate.
- OAuth: the sign-in standard used to authorize the connector: the person signs in with their own account, without sharing a password with the assistant.
- Schema: a group of tables inside the database (for example,
public). - SSL: encryption of the connection between Rowgate and the database.
- Read-only: a mode in which queries only read data, without changing, inserting or deleting anything.
- service_role: the Supabase service key, used by Rowgate to read the structure and query the project.
- Warehouse: the Snowflake or Databricks compute resource that runs the queries.