Juxtaboard manuals for project owners
Juxtaboard manuals for space owners
For the person who owns a space: sets up access, customers, channels, automations and payments, and decides who sees what.
Part of the documentation index.
Two parts:
User guide — how to run a space day to day. Organised by what you want to do.
Configuration guide — what each setting does, who can change it, and what can go wrong. Organised by menu item.
Russian versions live in ru/ under the same file names.
Words: these manuals say space, as the screens do. The address bar and the API say project. See the .
Start here
I want to… | Read |
|---|---|
Get a new space working | |
Add my team and decide who sees what | |
Find out why I can't see a menu item | |
Let customers sign in | |
Receive customer messages | |
Take payments | |
Back up, move or delete a space | |
Check my setup is safe | |
Understand tables, column types and formulas | |
Something isn't working |
User guide
Configuration guide
Who is who
Role | What they do | Where they read |
|---|---|---|
Space owner (you) | Sets up and governs one space | These manuals |
Team member | Works in the space | Their own screens; the "For your team" notes in each chapter |
Customer / partner | Signs in to the portal | What you send them |
Administrator | Runs the whole installation | |
Integrator / developer | Connects apps, scripts setups |
Conventions used in these manuals
Bold is a label you will see on screen, spelled exactly as the English interface spells it.
Code style is a right name, a value you type, or a file name.
Needs your administrator boxes mark things only the person who runs the installation can switch on. They say what to ask for and how to tell it is missing.
Careful boxes mark actions that cannot be undone or that grant trust to something outside your space.
Status
This is a first full draft. Every page was written from the product's code and its English interface strings and checked against them. It has not yet been walked through step by step in a running space, so treat step lists as accurate to the code, and report any screen that differs. Where the code could not settle a behaviour, the page says what was checked and does not claim more.
Written at commit 0dd530b1.