Registration takes 2 minutes. Right after it you get access to the admin panel, the editor and a Pro trial — no card required at this stage.
#Step 1 — Create an account
Go to lynkora.pro and click "Try for free", or open lynkora.pro/auth?tab=register directly.
The first screen has just one field — the account name — and two ways to create an account: via Google (fast, one click) or via email and password (the classic option).
#Option A — Create an account with Google (recommended)
The fastest path — under 30 seconds to a working admin panel.
- Enter your account name (for example, "Acme Corp" or "John Smith")
- Click "Create account with Google"
- Choose a Google account and agree to the consent screen
- LiKE creates your organization automatically:
- Owner — that's you (email and name from the Google account)
- Account address (slug) — generated from the "Account name" with transliteration and an availability check
- Email is already verified by Google — no OTP required
- You land in the admin panel right away; after a short onboarding, your Pro trial activates (14 days if you skip the survey, 30 if you complete it)
Why it's faster. The email is verified by Google (
email_verified=true), so LiKE skips the OTP step. You don't set a password — you always sign in through Google. If you later want to add an email password for a backup sign-in, you can do it in your User profile.
#Option B — Sign up with email
Click "Sign up with email" — the classic form with all fields expands:
#Form fields
| Field | Example | Notes |
|---|---|---|
| Company name | Acme Corp | Shown in the admin panel and in the UI header for all members |
| Account address (slug) | acme-corp |
The acme-corp.lynkora.pro subdomain. You can leave it empty — it will be generated automatically from the name (with Cyrillic transliteration) |
| [email protected] | The account owner's email (Owner role). Requires OTP verification (see Step 2). | |
| Password | — | At least 8 characters |
#Slug rules
- Lowercase Latin letters, digits and hyphens only
- Length: 3–40 characters
- Cannot start or end with a hyphen
- Reserved names are unavailable:
admin,api,demo,billing,support,status,www,app,platform,mail,static,cdn,root,system,like,lynkora - If the address is taken, the system suggests an available option (
acme-corp-2,acme-corp-3, and so on)
#GDPR consents in the form
The registration form has two checkboxes:
| Checkbox | Required? | What it means |
|---|---|---|
| "I accept the Terms of Service and Privacy Policy" | Required — without the check, the registration button is disabled | This is consent to process personal data under GDPR Art. 6 (the legitimate basis for all further work — storing email, profile, articles). The consent date and policy version are recorded in the database for compliance audit. |
| "I'd like to receive product news and updates by email" | Optional (off by default) | Consent to marketing emails (GDPR opt-in, separate from transactional messages). You can withdraw it at any time in User profile → Notifications. |
Links in the checkbox open in a new tab — a filled-in form is not lost.
Which option to choose. If your team already has a working Google Workspace (Gmail for business), choose Google: you can invite colleagues through the same provider and everyone has a single login. If your email is on your own domain but not via Google, choose email: the classic password flow, and you can connect corporate SSO later in Settings.
#Cookie consent
After the site first loads, a cookie banner appears at the bottom (after 2 seconds). Two options are available:
- Accept all cookies — functional + analytics (helps us improve the product)
- Only necessary — functional cookies for session operation and preferences
Your choice is saved to the user profile on the backend — after switching devices or signing in via incognito, the banner won't appear again. If we release a new version of the cookie policy, the banner returns for confirmation with a "policy updated" note. Details are in the Privacy Policy.
#Step 2 — Verify your email
An email with a 6-digit code arrives in your inbox. The code is valid for 24 hours.
- Didn't get it? Check your "Spam" folder or click "Resend" (a new code invalidates the old one)
- Fields advance to the next digit automatically as you type
- Paste is supported — copy all 6 digits and they'll fill in
After a successful confirmation, you land straight in your organization's admin panel.
#Step 3 — Pro trial and the onboarding survey
After your first sign-in to the admin panel, onboarding opens with a survey banner (4 short questions). The Pro trial activates when you complete onboarding — no payment and no card required. The duration depends on whether you take the survey:
- Complete the survey in full → 30 days of Pro
- Skip the survey → 14 days of Pro
All Pro features are available during the trial. When it ends, the organization automatically moves to Free.
#What the survey asks (4 steps)
| Step | Question | Why |
|---|---|---|
| 1 | Your role on the team | We adapt tips and the onboarding checklist for an admin / writer / team lead |
| 2 | What you want to solve with LiKE | To recommend relevant integrations and templates |
| 3 | Company name, team size, industry | To tailor the product (for example, templates for IT vs HR vs sales) |
| 4 | How you heard about LiKE | Marketing analytics — helps us allocate our efforts |
You can skip the survey at any point (the "Skip survey" button) — then the basic 14-day Pro trial activates. If you complete the survey later, the term extends to 30 days from the start date.
#Trial summary
When the trial ends, the organization automatically moves to Free (5 users, 100 articles, 50 AI requests per day). Your data is kept. You can pay for Pro at any time — see the Plans and billing article for details.
#Step 4 — Onboarding checklist
An interactive "Getting started with LiKE" checklist appears in the left panel, with progress in percent:
4 steps:
- Connect a knowledge source — Notion, Confluence, GitHub, GitLab, Wiki.js, or simply use the built-in editor
- Add your first article — via the editor or AI Author (see AI assistants)
- Try AI search — ask your first question via
⌘Kor the AI search in the sidebar - Invite a colleague — add at least one member to the team
You can collapse the checklist or hide it entirely with the "Hide" button — it doesn't get in the way and simply serves as a light guide at the start.
#Step 5 — Invite your team
- Go to Team in the sidebar
- Click "Invite"
- Enter an email and choose a role
- Copy the invitation link (valid for 7 days) or send it by email
| Role | Capabilities |
|---|---|
| Owner | Full access to the organization, billing and team. Cannot be removed (only transferred to someone else). |
| Admin | Manages content, team, integrations and settings. Does not manage the plan or billing. |
| Editor | Creates and edits articles, imports, and accesses the trash for their own articles. |
| User | View articles and search only. Does not see admin sections. |
| Guest | Guest access for external members: search and reading in the spaces they've been granted. |
Access is built from two axes: your role in the organization (Owner / Admin / Editor / User / Guest) and your role in the space (Admin / Editor / Viewer). One person can be an Admin in one space and a Viewer in another. Details are in Roles and access permissions.
#Step 6 — Choose your interface language
LiKE supports 25+ languages for AI search and 11 UI locales (ru, en, de, es, fr, it, pt, ko, sr, ar, zh).
- The interface language is changed in the top right corner via the
RU ▾switcher - The language of AI answers is determined automatically by the language of the question. If the language cannot be recognized (a very short or ambiguous query), the answer is given in the interface language. Language detection is a helper feature and may be inaccurate on short queries
- An RTL interface mode is available for Arabic
#Where to see consent status
Under Settings → Profile (the "Privacy" section) you can see:
- Consent to process personal data — policy version, consent date (required for compliance audit)
- Cookie consent — the current scope (
All/Only necessary), policy version, and a change button - Marketing emails — an On/Off toggle you can revoke at any time
All changes are recorded in the Activity log with resource_type=consent.