# Getting started This page takes an organisation from an empty account to its first session with minutes: create the account, choose the organisation name and plan, and hold a complete session in ten minutes with roll call, a vote and minutes. The linked concept pages explain each piece in detail. ## 1. Create the account 1. Open [/signup/](/signup/) and press **Continue with Google**. Ciserex stores no passwords: identity comes from Google through Amazon Cognito (PKCE flow). 2. On return from sign-in, the platform account exists with the Google name and e-mail. That e-mail owns everything created next. 3. Enter the organisation name and its identifier (*slug*). The slug uses lower-case letters, digits and underscores. It becomes the public address `.ciserex.com` and the internal identifier `app-ciserex-with-tenant-`. It cannot be changed later. 4. Choose the language (`es` or `en`) and the timezone. The language governs the interface, the bot messages and the minutes; the timezone governs the calendar. > The slug is part of every identifier the organisation owns. Choose a short, stable one: `congress`, `board_2026`, `room_3b`. ## 2. Choose the edition All four editions carry the complete system. None switches features off and none caps the roster: what changes is where the system lives and what contractual backing comes with it. | Edition | Where it runs | Members | Features | |---|---|---|---| | Trial | ciserex.com, thirty days, no card | unlimited | all | | Hosted | ciserex.com, operated by Ciserex | unlimited | all | | Self-hosted | your AWS account or your local network | unlimited | all | | Congress | dedicated deployment, agreed in writing | unlimited | all | A new organisation starts on **Trial**: thirty days with everything switched on, no card and no automatic renewal. When it ends you choose Hosted or Self-hosted; the records made during the trial are kept intact, the act log included. This site publishes no rates. The commercial terms of each edition — media and transcription-hour quotas included — are agreed in writing with the team: write to . While the platform is in pre-launch, the payment provider is a mock that returns `passed` for every transaction; nothing is charged. On confirming the edition, Ciserex creates the organisation (the *tenant*) with a default template, the initial analysis dimensions and the standard look. See [The organisation](#/concepts-tenant). ## 3. Enter the application The application lives at **app.ciserex.com**. It is one screen with tabs: **Calendar**, **Agenda**, **Roster**, **Archive** and **Configuration**. On the right opens the drawer of **the secretary**, the agent that answers questions and performs tasks with the permissions of the user asking. The calendar is the front door: sessions are created, opened and browsed from it. The other tabs show the state of the selected session. ## 4. First session in ten minutes ### Minute 0 to 2: create the session 1. In **Calendar**, click the desired day and time and choose **New session**. 2. Name the session and choose a template. For a first run, `board` or `poll` are the shortest. The six built-in templates are described in [Agenda templates](#/concepts-templates). 3. Save. The session is `PENDING` (scheduled) and its agenda items are materialised from the template. They can be edited in the **Agenda** tab: title, detail, decision mode, options and required majority. ### Minute 2 to 4: the roster The **Roster** tab decides who can be called and who can vote. - **Predefined** mode: add members one by one or import a CSV with name, e-mail, phone, group, seat and weight. Each member can link a Telegram account by following a deep link `t.me/?start=` that the secretary sends by e-mail or shows on screen. - **Ad hoc** mode: there is no prior list. Opening roll call shows a QR code; whoever scans it is entered into the roster of that session. Fields, modes and identity verification are explained in [The roster](#/concepts-roster). ### Minute 4 to 6: open the session and call the roll 1. In **Calendar**, select the session and press **Open**. The session enters the `rollcall` stage. 2. Press **Roll call**. Linked members receive a confirmation button in Telegram; the others confirm from the web. The list updates in real time: present, called without answer, absent, remote. 3. When the number present reaches the required quorum, the application says so: "84 of 128 members present. Quorum is met." Press **Start session**. The session becomes `ACTIVE`, stage `session`. ### Minute 6 to 8: a vote 1. In **Agenda**, open the first item of type `decision`. The item becomes `ACTIVE`. 2. Press **Vote**. The vote overlay slides up and the item becomes `PROCESSING`. Present members see the options on the web or as buttons in Telegram. 3. The visualisation updates with every ballot: hemicycle, grid, bars or diverging chart depending on the number of voters and the template. Ballots are immutable; if a member changes their mind before the close, the new ballot supersedes the previous one. 4. Press **Close vote**. Ciserex computes the tally, applies the majority rule and records the result on the item: `{ tally, passed, closed_at }`. The item becomes `ARCHIVED`. Majority and quorum rules, with worked numbers, are in [Majorities and quorum](#/concepts-majorities-quorum). How ballots work, in [Ballots](#/concepts-ballots). ### Minute 8 to 10: close and obtain the minutes 1. Walk through the remaining items or withdraw them. 2. In **Calendar**, press **Close session**. The session becomes `ARCHIVED`. 3. The close triggers the drafting of the minutes and the configured distribution pipelines. The session appears in **Archive** with its attendance, its results, its transcript if there was a recording, and the minutes in Markdown and PDF. The minutes use verbs of record: "Item 3 is approved by 71 votes in favour, 9 against and 4 abstentions." What is kept and what is published is described in [The archive](#/concepts-archive). ## 5. The secretary The secretary drawer accepts questions and orders in natural language: "Who has not confirmed yet?", "Open the vote on item 2", "Summarise the discussion on item 4". The secretary performs the same operations as the interface buttons, with the permissions of the user speaking to it, and never votes on anyone's behalf. Members linked through Telegram can write the same questions to the bot, scoped to their organisation. ## 6. What to configure next - **Configuration → Look**: logo and accent colour of the public site. - **Configuration → Roster**: default mode and verification method (`none`, `id`, `face`). - **Configuration → Transcription**: provider (Amazon Transcribe or OpenAI Whisper), language, number of speakers. See [Transcripts](#/concepts-transcripts). - **Configuration → Analysis**: sector and transversal dimensions. See [Analysis dimensions](#/concepts-dimensions). - **Configuration → Distribution**: pipelines that run when a session closes. See [Distribution pipelines](#/concepts-pipelines). For questions, [/support/](/support/) or support@ciserex.com. --- Next: [The organisation](#/concepts-tenant).