Create your workspace and sign in

Evodira is not self-serve. There is no public registration endpoint, and the form at /signup does not create anything. It composes a pilot request addressed to hello@evodira.com. That is deliberate: a workspace is a data boundary, and the first conversation is about where your content is allowed to live.

1. 1

   Request a pilot

   Go to /signup, fill in your name, organisation and work email, and submit. Your mail client opens with the request pre-written. If no mail client is configured, the address is shown as selectable text on the page, so copy it and send the mail yourself. Nothing is lost either way.

2. 2

   Receive your sign-in

   You are given an account against a control plane. For most customers that is evodira.com. Organisations running their own deployment get a plane of their own, and the address is in your welcome mail, and it is the same address your agents will talk to.

1. 1

   Open the sign-in page

   evodira.com/login, or your organisation’s own portal address if one has been published (see section 05). Enter your work email and password.

2. 2

   Enter your authentication code, if you have 2FA on

   The form asks for a six-digit code from your authenticator app. You will not see this step until you have turned two-factor on yourself. See section 06, and do turn it on.

3. 3

   Land in the console

   You arrive at /console, the control index: every surface you can reach, grouped by zone, with the ones waiting on a decision lit.

The first time you sign in with no workspace attached to your account, the console shows the creation form instead of the control index. You become the workspace owner.

1. 1

   Name the organisation

   The legal or trading name, such as Northwind Pay. An organisation can hold more than one workspace later; this is the outer container.

2. 2

   Name the workspace

   The team or estate this installation serves, such as Engineering. Slugs for both are generated for you with a short random suffix, so you never have to invent a unique identifier. A workspace named “Engineering” becomes something like engineering-wvr24.

3. 3

   Choose the region, carefully

   One of eu-west, us-east, us-west, uk, africa, apac. The region selects the store new content is written to and the inference location that serves this workspace.

4. 4

   Choose the sector

   Technology, financial services, healthcare, public sector, professional services, or other. It informs defaults and reporting; it does not gate anything.

5. 5

   Create

   The workspace is created, you are set as its owner, and the console reloads into the control index. You now hold all thirty permissions.

Open Settings and read the four blocks at the top before you invite anybody.

Workspace

Name, sector, region and status. Status ACTIVE is the only state that resolves. Suspending or archiving stops the workspace resolving at all, including for this console, which is why it is not offered as a toggle here.

Governance policy

Four values at a glance: publication (verified only by default), steward review (required), source permissions (enforce), and retention (365 days). Chapter 12 covers changing them.

People and roles

Everyone with a role in the workspace. On day one that is you, plus a service member per deployment profile. Those are the fleet service accounts, not humans.

Your account security

Two-factor state, password, and every browser currently holding a live session.

By default your people sign in at evodira.com/login. You can instead publish an organisation portal: a sign-in page at your own address, carrying your name, logo and colours. It exists so a person can check the address bar against something they recognise.

Two kinds of name, two different proofs

Evodira-managed

A label under a zone we operate, such as acme.evodira.com. You cannot create records there; we provision them. The name is yours because the platform recorded the claim. It already resolves and already has a certificate, so you call verify and then publish, with nothing to wait on.

Your own domain

A name in your DNS, such as knowledge.acme.com. We cannot create records there; you can. You add a DNS TXT challenge record, we observe it, and only then may the name be published.

1. 1

   Open Settings and find Organisation portal

   It sits directly under the workspace block on Settings.

2. 2

   Choose the hostname

   Either accept the managed name or enter one of your own. Use Use a different name to change a name you have already claimed.

3. 3

   Prove control

   For a managed name, press verify. The proof is the platform’s own record. For your own domain, publish the TXT record shown and then verify. The state moves unverified → pending → verified, or failed.

4. 4

   Publish

   Only a verified name may be published, and a database constraint enforces the pairing, not a service call somebody can forget.

5. 5

   Brand the page, and mind what you put on it

   Accent colour, background, strapline (plain text, 200 characters, no angle brackets), support link, logo, wordmark and favicon (PNG/JPEG/WEBP; 512 KB for logo and wordmark, 64 KB for the favicon). Images are uploaded to Evodira. There is no field for an image URL of your own, because a login page that loads a picture from a third-party host hands that host a record of every visit.

6. 6

   Optionally set the workspace the portal opens

   A hint for the sign-in page, never an entitlement. A member is still matched to their own membership before they see anything, so choosing a workspace here cannot give anybody access to one.

You are the owner. Your password is currently the only thing between somebody who has it and everything this workspace can see.

• Turn on two-factor. Settings → Your account security → Turn on two-factor. Scan the code with an authenticator app and confirm with a six-digit code.
• Know that changing your password does not sign out your other sessions. If the reason you are changing it is that somebody may know the old one, use Sign out everywhere else as well.
• Read the session list. Every browser holding a live sign-in, with its address and when it started. A session you do not recognise is the clearest signal you will get that your password is known to someone else.