Database Configuration

Database Configuration is the one screen where you change what your contact records hold — the fields, how they are grouped, which ones show as table columns, and the action buttons on every row. It opens over whichever contact list you are looking at, and nothing is written until you press Save changes.

Before you start

Two separate permissions control this screen, and Raion Hub hides the controls you do not have rather than greying them out. If a button this guide names is simply not there, that is why.

Table Settings — fields, sections and row actions
Views — adding a database, renaming one, pinning, and turning columns on and off

Everyone can open this screen on Leads. If the footer reads View only — you don’t have permission to change this configuration. and the only button is Close, ask a Workspace Owner to give you those permissions in Settings → Roles.

The four things this screen controls

Thing	What it is	Where a change lands
A field	One piece of information on a contact — a name, a budget, an appointment date. Defined once for the whole workspace, then added to the databases that need it.	Renaming a field, or changing its type, changes it everywhere
A database	A saved view over one shared pool of contacts. It decides which fields show, in what order, which are pinned, and which contacts qualify for it.	That database only
A section	A group of fields on a contact’s record card.	That database only — each database has its own sections
Row actions	The buttons on the right-hand rail of every row. One ordered list.	Every database

Every database reads the same field library. What differs between two databases is which of those fields each one shows, and how it groups them into sections.

Steps

Find the database in the sidebar

In the sidebar, under the Database group heading, hover the database you want to change. A sliders gear appears at the right of the row; its tooltip reads Configure Leads fields for the built-in Leads database. On a phone or tablet the gear is always visible.

The gear appears on the row when you hover it — it is not there when the sidebar is collapsed to the icon rail

Click the gear

Database Configuration opens over the list you were on, already pointed at that database. The address bar does not change.

Left to right along the top: the Library chip, one chip per database, then Add database. The right pane is a live Preview of the record card

Other ways in

Any of these opens the same screen, just landing somewhere different.

Where	What to click	Where you land
Sidebar, the Database group heading	The + (Add database)	The New database form
Top right of the contact list, on a computer	The Tools chip, then Database Config	The top of the field list
The filter bar, on a phone	The View & Tools chip, then Database Config	The top of the field list
Any table column header	Its chevron, then Edit field…	That field’s editor, already open
Any table column header	Its chevron, then Add column…	A blank new field in the Other section
The table’s Actions column header	The gear (Configure row actions)	The Actions list

The last three need the Table Settings permission, so they are missing entirely without it.

Nothing saves until you press Save changes

Every edit you make is held locally and applied in one batch when you save. That is why the table behind the screen previews your change before you commit it. Read the footer to know where you stand.

The footer says	What it means
All changes saved	Nothing is waiting. Save changes is greyed out
An amber dot and Unsaved changes	You have edits waiting. Save changes is live
View only — you don’t have permission to change this configuration.	You can look but not change. The only button is Close

Underneath, in both of the first two states: Changes are saved together when you hit Save.

An amber dot is your cue that something is still only local

On a successful save a toast reads Database config saved. If the server refuses part of it you get Some changes could not be saved - reloading the latest config. and the screen reloads what is actually stored — so the refused edit visibly reverts.

Three things do not wait for Save changes.

Pressing Create field — the field is created on the server right then so it has a real identity to hang settings on. Discarding afterwards deletes the fields you created in that sitting.
Adding or removing a database.
Renaming, archiving, merging or deleting a lead source.

Discard will not undo the last two. Undo them by hand.

Closing the screen

Esc, and your phone’s back button or edge-swipe, step back one layer at a time: out of a single action’s editor, then the Actions list, then a field editor, then a section editor, then the New section form, then the database form, then the preview sheet, and only then the screen itself.

The X and a click on the dimmed background do not step back. From any depth they close the whole screen. If you have unsaved edits you are asked Discard changes? first — Your unsaved changes will be reverted to the last saved configuration. This can’t be undone.

What to change first

Add, edit and remove a field Choose a field type Group fields into sections Choose and pin your table columns Set up a dropdown's options and colours Set up the row action buttons

If something goes wrong

What happens	Why	What to do
The gear, Add field or section or Add database is not there	The permission is missing, and Raion Hub hides the control instead of disabling it	Ask an owner for Table Settings (fields, sections, actions) or Views (databases, pinning, column visibility)
The footer says View only — you don’t have permission to change this configuration.	You have neither permission	Same as above. Your only button is Close, not Cancel
Rows will not drag and the eye buttons are gone, but the field editor works	You have Table Settings but not Views — reordering, hiding and pinning are written by the other permission	Ask for Views
The switcher row shows only one database	Without Views, you see the built-in database only	Ask for Views
A change vanished after saving, and a toast explained why	The server refused that one piece and the screen reloaded the stored version	Read the toast. Common causes are removing a dropdown’s default option, and a section that has hit its field cap
Database config saved, but the table looks unchanged	The edit was to the record card, not the table. A field can sit in a section without being a column	Turn that field’s eye on — see Choose and pin your table columns
You clicked the X three editors deep and lost everything	The X closes the whole screen from any depth	Use Esc to come back one layer at a time