Setting up the Team Space
A Team Space is a perfectly normal ApptiveGrid Space — with two special traits: it carries the category apptiveTeams, and its configuration Grids are discoverable by Keys.
Marking a Space as a Team Space
In the Space settings, set the category to apptiveTeams.
Without this category, the Space won't appear in the app
The app only offers Spaces with the category apptiveTeams for selection. If someone sees "no team," that's the first thing to check — the second is whether they're even a member of the Space.
The Space needs the Pro plan
The app only offers team Spaces on the Pro plan. A Space on the Free plan appears in the list but cannot be opened; the app shows a notice instead. → Plans and seats
Keys: how the app finds its Grids
A Key is a readable identifier that Grids and fields can carry in addition to their name. The interface explains it like this:
A Key is a readable identifier for this Grid. It can be used to connect a Grid to an app.
That's exactly what ApptiveTeams uses. The app doesn't look for Grids named "Configuration" or "Tabs" — it looks for Grids with the Keys config, tabs, and settings. You're free to name them however you like, and to rename them at any time.
| What | Where you set the Key |
|---|---|
| Grid | Grid menu (⋮) → Manage Grid Key |
| Fields | View menu (⋮) → Manage Field Keys |
| Individual field | Column menu → Change column Key |
Keys must be written exactly
Case matters. primarycolor is not primaryColor, and an accidental space makes a Key unusable. A faulty Key doesn't show up as an error message — content simply goes missing in the app.
The three configuration Grids
Inside the Team Space, the app expects three Grids:
| Grid Key | Purpose |
|---|---|
config | The app's branding: logo, primary color, version |
tabs | The tabs in the bottom navigation bar |
settings | Additional entries on the settings screen |
On top of that come the content Grids linked from the tabs — one Grid per tile or card tab. These don't need a Grid Key, since they're found through a link. → Set up tabs
Views work too
As a configuration Grid, you can use either a regular Grid or a View. If the app finds both with the same Key, the View wins.
That's useful: a filtered View lets you hide content without deleting it — for example, news items with a Published checkmark.
Setting branding: the config Grid
The Grid with the Key config controls the app's appearance. Only the first row is evaluated.
| Field Key | Field type | Required | Description |
|---|---|---|---|
logo | Files (Image) | yes | Your company's logo, shown e.g. above the Tile view |
primaryColor | Text | yes | Primary color as a hex value, e.g. #1565C0. Colors icons, buttons, and the active tab indicator |
version | Text / Number | no | Version of the Team Space schema. Currently 1; assumed to be 1 if left blank. A value higher than the app knows shows the message "Update required" |
If the logo or color is missing, no branding is applied at all
The app only evaluates the configuration row if both required fields are filled in. If one is missing, the entire row is discarded — the app then starts with no logo and no color, not just without the missing piece.
The color must be a hex value. A color name like blue doesn't work.