Add a database
Build a second, named view over the contacts you already have — a Customers board, a Landlords list — with its own rule for who belongs in it and its own columns. Takes about five minutes.
Before you start
- Creating a database needs the Views permission with create. The + in the sidebar is there for everyone, but without that grant it opens Database Configuration without the create form — ask a workspace owner if that is what happens to you.
- Have a rough idea of the rule: which of your existing contacts belong in this database. You can leave it empty for now and set it later.
Steps
Open the create form
In the sidebar, hover the group header Database. A + appears at its right edge — its label is Add database. On a touchscreen it is always visible. Click it.
Hover the Database group header to reveal Add database
Database Configuration opens with the New database panel already on screen, so there is no detour.
The longer way round, if you are already inside a database: the Tools chip → Database Config → then the Add database chip in the row across the top of the window.
Name it
Type into Database name. Press ↵ to submit, or Esc to back out.
The name is used in more places than the sidebar. The create button in the top bar becomes Add plus the singular of your name — a database called Customers gives you Add Customer. Raion Hub works the singular out from what you typed, so an unusual name can come out oddly; it is still your workspace’s own word rather than a generic “Lead”.
Database Configuration → New database
Pick an icon
Under Icon, type into the search box — Search icons — try ‘ai’, ‘deal’, ‘appointment’ — and the grid below narrows as you type. The line under the grid keeps count: 3 matches, or No matches — try different keywords. when nothing hits. Click an icon and its cell tints.
The icon is decoration only. It appears on the sidebar row, on the chip inside Database Configuration, and on the mobile switcher. Skip this step and the database gets a bookmark.
Decide who belongs in it
Under Show records where, click the pill that reads Field, pick a field, and set the condition. Everything you add here has to be true for a contact to appear in this database.
Leave it completely empty and the database contains every contact in the workspace — which is a perfectly reasonable thing to want.
This is the same builder as the toolbar’s filter panel, down to the operators, so Find the contacts you need explains every one of them.
Show records where — the rule that decides who is in this database
Create it
Click Add database. You cannot click it until the name field has something in it.
The database is created straight away — name, icon and rule together. The chip row at the top jumps to your new database, and a new row appears in the sidebar under Leads. Close the window and you are standing in it.
Add its columns
A brand-new database starts blank. Its only column is Name, which is always there and always pinned. It does not inherit the columns from Leads.
To add the rest, click a column header in the new database’s table and pick Add column… — you will not see that row unless your role has the Table Settings permission with update.
The same fields are listed inside Database Configuration: click this database’s own chip in the row across the top of the window to reach its field list, or the Library chip beside it for the workspace-wide list of every field you have.
A new database starts with Name only — add the columns you need
What each part of the form does
| Part | What it does |
|---|---|
| Database name | Names the sidebar row, the create button (Add Customer) and the database’s empty-state wording |
| Icon | Decoration — the sidebar row, the configuration chip, the mobile switcher |
| Show records where | The membership rule. Conditions in one group all have to be true; a second group means “or this set instead” |
| Columns (this Tab) | A read-only note, not a control. Which columns this database shows is edited from its own field list |
Good to know
- Everything else inside Database Configuration is held until you press Save changes — the footer tells you All changes saved or Unsaved changes, with the reminder Changes are saved together when you hit Save. Creating a database is the one exception: Add database saves immediately.
- Databases are visible to the whole workspace. There is no per-database sharing to set up.
- At most three columns can be frozen in any one database, and Name is always one of them — see Work in Table view.
- Renaming and re-icon-ing a database later is the same panel, titled Edit database instead.
If something goes wrong
| What you see | Why | What to do |
|---|---|---|
| Couldn’t create this Tab — try again. inside the panel | The server refused the request | Your name, icon and conditions are all still there — press Add database again |
| The sidebar + opens Database Configuration, but no create form | Your role does not have Views create | Ask a workspace owner to grant it |
| Clicking the active database’s chip does not open an edit form, and no pencil shows | Renaming, re-icon-ing and re-ruling need Views update | Ask a workspace owner to grant it |
| No Remove Tab button when you edit a database you built | Removing is a separate grant from renaming — it needs Views delete | Ask a workspace owner |
| The footer reads View only — you don’t have permission to change this configuration. and offers only Close | Your role cannot change any of this configuration | Ask a workspace owner |
| A warning dot and Unsaved Tab changes beside the rule | You changed the rule and have not saved it | Press Save database — or Add database if you are still creating it — before you leave |
| Editing Leads shows built-in and admin only, and no remove | The base database cannot be removed | Use Reset to default if you want its rule back the way it started |
Next
- Work in Table viewTable view is the spreadsheet-style list: one row per contact, one column per
- Find the contacts you needFour controls in the toolbar decide who you are looking at: Owner (whose
- Work the board in Kanban viewKanban lays your contacts out as cards in columns — one column per stage — so you