Skip to content

Projects

A project is your workspace in Ekit. Everything lives inside it:

In a project What it is
Tables Your content, organized like a spreadsheet: one table per content type (articles, products, team members…) — see Fields
Entries The rows of a table, with a value per field — and per language for multilingual fields
Sites Websites rendered by Ekit from Handlebars templates, fed by your tables — see Datasources
Languages The languages of your content, with one default language
Collaborators People you invite to work on the project with you
API token The key to read your content from another application — see Public API

You can own several projects and be invited to other people's projects. The number of projects you can own depends on your plan — see Plans & limits.

Create a project

  1. Open the project selector at the top of the left menu and choose New project (or use the command palette: Ctrl+K / Cmd+K).
  2. Enter a project title (2 to 100 characters) and, optionally, a description.
  3. In Input languages, tick the languages of your content and choose the default language. Your browser language is preselected.
  4. Click Create project: you land on the project dashboard.

Choose your languages carefully

The languages of a project are set when it is created and cannot be changed afterwards from the Studio. The number of languages per project depends on your plan.

The project dashboard

The dashboard is the home page of a project:

  • Current project: its languages, the number of tables and sites, and shortcuts to manage them;
  • Get started with Ekit: a six-step checklist — project, table, field, entry, site, preview — that you can hide once you are comfortable;
  • Quick start: links to this documentation and to the video demos.

Switch between projects

The project selector at the top of the left menu lists My projects (the ones you own) and Shared with me (the ones you were invited to), with a filter to find a project quickly. The command palette (Ctrl+K / Cmd+K) also lists your projects, tables and sites.

Interface language and content language

Ekit uses two different languages:

  • the interface language — menus and buttons of the Studio;
  • the input language — the language of the content you are reading and editing. Change it with the language selector in the header (for example EN): the grid, forms and sites then show and save that language.

When you switch to another project, the input language is reset to that project's default language if the previous one is not available.

Project settings

Open Settings in the left menu. The settings page contains:

  • Project basics — title and description.
  • Input languages — the project's languages (read-only after creation).
  • Project token — the key used by the Public API. It is shown only once: copy it and keep it safe. Regenerate creates a new token and immediately revokes the previous one: applications that use the old token stop working.
  • Collaborators — invite people by email with a role, change a collaborator's role, remove a collaborator or cancel a pending invitation, and see how many seats are used, pending invitations included (for example “3 / 5 collaborators (including 1 pending invitation)”). See Collaboration. Settings are available to the owner and admins.
  • Export the project — download the whole project in one ZIP: data, files and site code. See Export your data.

Delete (in the page header) permanently deletes the project: its tables, entries, files and sites. This cannot be undone — export the project first if you may need its content later.

Roles

Everyone in a project has a role. The person who created the project is its owner; each collaborator gets a role chosen when you invite them (Editor by default), and an admin can change it at any time in Settings → Collaborators.

Action Owner Admin Editor Viewer
See tables and entries, export a table (XLSX) ✓ ✓ ✓ ✓
Add, edit, delete and translate entries; upload files ✓ ✓ ✓ —
Create and edit tables and fields, reorder columns, import data ✓ ✓ — —
Sites: editor, AI assistant, forms, Methods, secrets, domains, statistics ✓ ✓ — —
Project settings (title, languages) ✓ ✓ — —
Invite collaborators, change roles, remove a collaborator ✓ ✓ — —
Use the project chat, see who is online ✓ ✓ ✓ ✓
Generate or regenerate the API token ✓ — — —
Export the whole project ✓ — — —
Delete the project, change the plan ✓ — — —
  • Editor is the right role for people who keep the content up to date (a team entering contacts, a restaurant updating its menu): they work in the tables but don't see the sites or the settings.
  • Viewer is for people who only need to look at the data or export it.
  • Admin can do everything except what belongs to the owner: the plan, the API token, the full export and deleting the project.
  • Collaborators invited before roles existed are Admins: nothing changed for them.

Roles are checked by the server on every action, including real-time updates: hiding a button in the Studio is only a convenience. When a role doesn't allow an action, Ekit says so with a message — you stay signed in.

When an admin changes your role, the Studio updates at once (menus, buttons). When you are removed from a project, it disappears from your list.

Limits always follow the owner's plan: when a collaborator creates a table or an entry, it counts towards the owner's plan.