Accounts
What an account enables, and what you can use without signing in
Anyone with an email address or a Google account can create a Queria account for free. Your account is created the first time you sign in.
What you can use without signing in
Browsing and analyzing data works without signing in.
| Feature | Sign-in |
|---|---|
| Searching and browsing datasets | Not required |
| Querying and analyzing with SQL | Not required |
| Visualization (charts and maps) | Not required |
| Reading Showcase reports | Not required |
| Fetching and analyzing data from the CLI | Not required |
| Seeing how many people starred something | Not required |
| Starring something | Required |
| Seeing how many followers an account has | Not required |
| Following an account | Required |
| Reading comments | Not required |
| Writing comments | Required |
Issuing API tokens (including queria login) |
Required |
| Account settings | Required |
What an account enables
Signing in gives you access to the following features.
- Issuing API tokens — relax the rate limits for access from external tools and the CLI, free of charge. See Authentication for how to issue and register tokens
queria login— obtain and save a token from the CLI with browser approval alone. Fetching and analyzing data with the CLI itself works without signing in- Stars — star datasets and tables, and the reports, maps and dashboards others have published, then reach them all from the home page or
queria.io/stars. What you star also appears on your profile (see below) - Follow — press “Follow” on another person’s or organization’s account page, and the reports, maps and dashboards that account publishes are listed at
queria.io/following(“Following” in the account menu), newest first, up to 50. Reports are ordered by the date they were published, and maps and dashboards by the date they were last saved. Account pages show the number of followers; who follows an account is not shown. You cannot follow your own account or an organization you are a member of - A home page of your own — once signed in, the top of the site becomes an entry point to your own work. See Home page
Your account pages
Once signed in, these pages are available. <handle> is the handle you chose at your first sign-in.
Account, Dataset list, Stars (public) and People are visible to anyone, so they open without signing in.
The rest are yours alone, and an organization’s settings open only for its admins.
| Page | URL | Contents |
|---|---|---|
| Home | queria.io |
Links to analysis tools, your reports, recently viewed, stars, and your own datasets |
| Stars (manage) | queria.io/stars |
Everything you starred |
| Following | queria.io/following |
Reports, maps and dashboards published by the accounts you follow |
| Account | queria.io/accounts/<handle> |
Your profile |
| Dataset list | queria.io/datasets/<handle> |
The datasets you have published |
| Stars (public) | queria.io/accounts/<handle>/stars |
The stars you show publicly |
| People | queria.io/accounts/<handle>/people |
Who belongs to an organization account |
| Account settings | queria.io/settings |
Display name, avatar, bio, homepage, links, sign-in method, account deletion |
| Plan and usage | queria.io/settings/plan |
Plans for you and your organizations, the features you can use, and your storage. If you have credits, the balance, what remains of each grant and when it expires, usage in the last 30 days, and whether to keep going and pay with credits once the allowance of a paid plan is used up, for you and the organizations you administer |
| Connections | queria.io/settings/connections |
The URL and commands for connecting from an AI chat, the Queria CLI or DuckDB |
| API tokens | queria.io/settings/tokens |
Issuing and revoking tokens |
| Organizations | queria.io/settings/organizations |
The organization accounts you belong to, and accepting invitations sent to you |
| Organization settings | queria.io/accounts/<handle>/settings |
An organization’s display name, avatar, bio, homepage and links (admins only) |
| Organization tokens | queria.io/accounts/<handle>/settings/tokens |
Issuing and revoking organization service tokens and GitHub Actions registrations (admins only) |
| Organization teams | queria.io/accounts/<handle>/settings/teams |
Creating and deleting teams, adding or removing their members, and choosing maintainers. You can share reports, maps and dashboards with a team (admins and team maintainers) |
Your own settings (account settings, plan and usage, API tokens and organizations) are linked from a menu on the left of the screen.
Profile
queria.io/accounts/<handle> shows who an account is and what it has published. It opens
without signing in.
Tabs run along the top, and the left column stays in place whichever tab you are on.
| Tab | When it appears | Contents |
|---|---|---|
| Overview | Always | Recent reports (only those you can see; your own private reports included for you), recently updated datasets, organizations you belong to (personal accounts), members (organization accounts). On your own account with no datasets or reports yet, a short guide to getting started |
| Datasets | Always | The datasets this account has published |
| Reports | Always | The reports this account has published. Members-only and private reports appear only to people who can open them |
| Maps | Always | The maps saved from area analysis. Maps visible only to their owner appear only to the person who saved them |
| Dashboards | Always | The dashboards this account has. Members-only and private dashboards appear only to people who can open them |
| Stars | Personal accounts only | The datasets, tables, reports, maps and dashboards this account starred |
| People | Organization accounts only | Who belongs to the organization |
| Settings | Organization admins only | Editing the displayed information, and token management |
The left column shows the avatar, display name, handle, bio, homepage and links. Without an avatar image, the initial of the display name is shown. Everything from the bio down appears only once you have filled it in from account settings. For an organization account, an admin edits the avatar, display name, bio, homepage and links from the Settings tab.
Stars are public
Anyone can see who starred which dataset, table, report, map or dashboard, from that account’s profile. Only datasets, tables, reports, maps and dashboards that are currently public appear there.
Teams and maintainers
Organization admins can group members into teams. You can share reports, maps and dashboards with a team.
- Admins create and delete teams and choose maintainers. Click the shield button next to a team member’s name to make them a maintainer or a member again
- Maintainers can add and remove members of the teams they maintain. Only admins can remove other maintainers
- Maintainers open the teams page from “Manage teams” on the organization’s “People” tab
Who can access an organization’s datasets
By default, every member of an organization can read and write its private datasets. On the organization plan, admins can limit each dataset to the people and teams it is shared with.
- When an admin opens a dataset page, a “Member access” section appears. Click “Limit to shared people and teams” to restrict the dataset, and “Open to all members” to undo it
- To share a restricted dataset, pick a member or team and a permission, then click “Share”. “Read” can only read the data; “Write” can also write new versions
- Admins can read and write every restricted dataset. Only admins can change its visibility or delete it
- Members it is not shared with do not see the dataset anywhere: not on its page, in lists, in SQL, or in AI chat
- The organization’s service tokens can still write to restricted datasets
- Shares are removed when a member leaves the organization. When the organization plan contract ends, admins can no longer restrict or share datasets, but they can still open datasets to all members and remove shares
Contract seats
When an organization’s plan contract sets a number of seats, admins cannot send an invitation that would make members plus pending invitations exceed it. Admins see the seats in use in the invitations section of the “People” tab. When all seats are in use, revoke an unused invitation or ask the Queria team to add seats. Lowering the seat count does not remove current members.
What the People list shows
The People list shows display names, handles and roles only. Email addresses are never shown, not even to admins.
Next steps
- Home page: the signed-in home page and stars
- Signing in: how to sign in, and what to check when you cannot
- Pricing: what you can use for free
- Authentication: issuing and registering API tokens
