11 — Glossary
This is a one-page decoder for the domain vocabulary used in the codebase, the URLs, and the conversations on this team. Most of these terms are not standard social-media-management vocabulary — they are Someli-specific or have Someli-specific meanings. When you see a term you don't recognise, look here first.
Where a term has a documented "verify with the team" status, the entry below reflects best-effort inference from the code rather than authoritative product knowledge.
Identity & accounts
| Term |
What it means |
| member / user |
The human logging in. Identified by memberId / id / useid. Can belong to multiple accounts. |
| account |
A workspace that owns posts, brand kits, social accounts, etc. Identified by accountId. URL-scoped: most authenticated routes are /<accountId>/.... A user has a "current" account selected via the account switcher. |
| account owner |
A user with roleType === 5. Has billing-management privileges. |
| invited user |
A user with isInvited === 1. They joined an existing account by accepting an invite, not by signing up. Bypasses owner-only billing redirects. |
| impersonation |
Admin-side feature that lets staff log in as a user without the user's password. Marked by impersonationLogin cookie = true. Suppresses several side effects (no updateProfile, no payment redirect). |
BNI / noId |
A user marked as part of a special cohort (likely "Business Network International" — verify with the team). When userData.noId is truthy, the launch and $1 plans are filtered out and only yearly-billing options surface. See helpers/helper.js → getPlanList. |
| role types |
roleType field on the user, used for authorization. Known values: 1 (member), 5 (owner), 11 (some elevated role). See 12-permissions-and-roles.md. |
| account_role |
A second authorization field. account_role === 3 = restricted role; head.js blocks library and ROI/overview routes for this role. |
Onboarding
| Term |
What it means |
| onboarding flow |
A backend-defined sequence of pages a new account must complete. The default fallback (in mixins/onboardingNavigation.js) is subjects_services → Organisationprofile → brandkit → payment. |
Onboarding_type_id |
Selects which onboarding flow to show. Different audiences (BNI, regular signup, partner signups, etc.) get different flows. Persisted in accountdetails cookie and the Vuex onboarding module. |
| landing_url |
Server-driven post-login redirect target. Returned by /auth/getaccountdetails. New accounts mid-onboarding land on the next-incomplete-step URL; complete accounts land on /contentplanner. See 03-auth-and-sessions.md. |
| Organisation profile |
Onboarding step where the account's company info is captured. Page: pages/_accid/Organisationprofile. Backed by /auth/getCompanyData / /auth/AICompanyData / /process-organization-profile etc. |
| subjects & services |
Onboarding step where the user picks the topics/services their account will produce content about. Page: pages/_accid/subjects_services. Backed by /auth/getRecommendedTopics, /auth/chooseRecomSubject, /auth/getUserChosenSubjects. |
| goals & objectives |
Onboarding step capturing the account's marketing objectives. Page: pages/_accid/goals_objectives. Backed by /getGoalsObjects, /auth/getAiObjective, /auth/approveObjective. |
| chapter (chaptername) |
Onboarding step. Verify with the team — chapter is BNI-vocabulary for a local group. Page: pages/_accid/chaptername. Backed by /generate-chapter-profile, /update-chapter-profile, /auth/approveChapterData. Likely BNI-flow specific. |
| brand kit |
Stored set of brand assets (logos, colours, fonts, templates). Page: pages/_accid/brandkit. Backed by /auth/getLogo, /auth/uploadLogo, /auth/savecolorset, /auth/saveFont, /auth/brandTemplateSet. |
| brand positioning |
The marketing/voice positioning statement for the account, used by AI generators. Backed by /auth/getBrandPositioning, /auth/getAiBrandPositioning, /auth/replaceAIBrandPositioning, /auth/approveBrandPositioning. |
| tone of voice |
Per-account writing style preset (formal, casual, etc.). Used by AI text generation. Cached via api/fetchToneOfVoice. Endpoint: /getToneOfVoice. |
Content & posts
| Term |
What it means |
| post |
A unit of content scheduled for one or more social platforms. Has a status (see 13-post-lifecycle.md) and a channeldata array containing per-platform sub-statuses. |
| carousel post |
A multi-image post (Instagram-style carousel). Edited in pages/_accid/carouseleditor. Has its own backend endpoints (/auth/getcarousalpost, /auth/userScheduleCarousal). |
| DIY post |
"Do it yourself" post template. Cached via api/fetchDIYPost. Endpoint: /getDiy_text. Verify with the team what distinguishes this from a regular template. |
| reel idea |
Short-form video idea folder. Cached via api/fetchAllReelIdeas. Endpoint: /auth/getAllReelIdeasFolder. Companion modal: ReelIdeasModal.vue. |
| shared image / template |
An asset shared across accounts in an organisation. Endpoints: /auth/getAllSharedImages, /auth/getAllSharedFolderImages, /auth/getAllSharedFolderTemps. Cached via api/fetchSharedImages. |
| my library |
The user's personal saved-content folder. Endpoint: /auth/getAllLibrary, /auth/getMyLibraryPost/<page>. Cached via api/fetchLibraryPosts and api/fetchImageLibrary. |
| template / template set |
Reusable design template. Endpoints: /auth/brandTemplateSet, /auth/addUserFolderTemplatesById, /auth/getAllSharedFolderTemps. |
| content folder |
User-organised group of posts/templates. Endpoints: /addOrUpdateUserFolder, /archiveContentFolder, /auth/getAccountWebsiteFolders. |
| scheduled post status |
A post's place in the publishing lifecycle. Values: BRANDING, INSERTED, SCHEDULED, POSTED, FAILED, POSTED_WITH_ERROR, PENDING. See 13-post-lifecycle.md for the full diagram. |
| approval / approved |
A post moves from SCHEDULED (approved=0, "Needs approval") to SCHEDULED (approved=1) before it can publish. The approver is typically the account owner or a designated reviewer. |
| partial publish |
Post status the UI shows when channeldata contains both POSTED and FAILED entries. Encoded as POSTED_WITH_ERROR in helpers/helper.js → calStatus. |
| branding |
Status used while AI generates a branded version of a post (logo overlay, brand colours). Visible in the calendar as the BRANDING state. |
| content planner |
The calendar/scheduling UI. The product's primary surface. Page: pages/_accid/contentplanner. Uses FullCalendar. helpers/helper.js → calStatus is the colour-coding source of truth. |
| approved dates |
Dates on which approved posts are scheduled to publish. Cached via api/fetchApprovedDates. Endpoint: /auth/getApprovedDates. |
| event posts |
Posts tied to a calendar event/holiday. Endpoints: /auth/getEventposts, /auth/getALLEventposts, /auth/scheduleEventposts. Companion: HolidaySelectionModal.vue. |
Dashboards & analytics
| Term |
What it means |
| dashboard / overview |
Aggregate metrics view. Pages under pages/_accid/dashboard/. Sub-sections: ROI, Reach, Leaderboard, Hashtag Analytics, Website Traffic, Google Reviews, Leads, New Connections, Action Items, Roadmap. |
| ROI |
Return-on-investment dashboard. Page: pages/_accid/dashboard/roi. Restricted from account_role === 3. |
| reach |
Audience reach metrics. Page under dashboard/reach. Has its own Vuex module (store/reach/). |
| leaderboard |
Comparative metrics across accounts/members. Page under dashboard/leaderboard. Vuex module: store/leaderboard/. |
| hashtag analytics |
Performance breakdown by hashtag. Page under dashboard/hashtag-analytics. |
| action items |
Outstanding tasks for the account (approvals due, posts to review, etc.). |
Network features
| Term |
What it means |
| Someli network |
A community/social surface inside the app. Layout: layouts/someliNetwork.vue. Page tree: pages/someli_network/. Verify with the team for product-level intent — distinct from public social platforms. |
| circle network |
A separate, related network feature. Page: pages/_accid/contentplanner integrates with it; helper at helpers/circleNetworkHelper.js. Companion modal: CircleNetworkModal.vue. Verify with the team how this differs from the Someli network. |
Billing
| Term |
What it means |
| plan |
A subscription tier returned by the backend. Filtered client-side by helpers/helper.js → getPlanList based on noId and signup-date cohort. Constants: PLAN.LAUNCH = 7, PLAN.ONE_DOLLAR = 28 (constants/constants.js). |
| billing period |
Monthly / yearly. Constant YEARLY_BILLING = 6. The plan filter treats yearly as always-eligible. |
| paddle txn / sub_id |
A pending Paddle transaction is held in the paddleTxnId cookie. A successful subscription is identified by sub_id (cached in subs cookie via api/fetchSubscription). The redirect middleware uses both to decide whether to send the user to /payment. |
| trial period |
trialPeriod >= 0 means the plan has a free trial. Surface plans with this flag for new users. |
| impact conversion |
Affiliate / partner attribution event. Endpoints: /auth/impact-conversion, /auth/cancel-impact-conversion. Companion: FirstPromoter on the marketing side. |
| Term |
What it means |
| provider |
A social network. Identified by integer ID in constants/constants.js → PROVIDER: Facebook=1, Twitter=2, Instagram=3, LinkedIn=4, TikTok=6. (5 is intentionally skipped — verify with the team.) |
| social link / sociallink |
Linking the user's account to a social-network identity. Endpoint: /sociallink. Companion middleware: middleware/sociallink.js. |
| social account / channel |
A connected provider on the user's account, used to publish posts. Plural: a post's channeldata array contains one entry per published-to channel. |
| token refresh |
Periodic refresh of provider tokens to keep posting alive. Endpoint: /tokenRefresh. Triggered after sociallink for Facebook (1) and Instagram (3). |
| Meta |
Facebook + Instagram together (under Meta's API umbrella). Reconnection logic handles them as a pair — see commit log "improve Meta account reconnection logic". |
Editor & design
| Term |
What it means |
| Polotno |
Third-party design SDK. Powers the design canvas in polotno-editor/. See 06-polotno-integration.md. |
| post editor |
The editor for a single post. Page: pages/_accid/posteditor/_id/. Mounts the Polotno bundle. |
| carousel editor |
The editor for multi-image carousel posts. Page: pages/_accid/carouseleditor/_id/. Mounts the Polotno bundle. |
| user editor / user-media editor |
Editor variants for user-uploaded media. Pages: pages/_accid/usereditor/_id/, pages/_accid/usermediaditor/_id/. |
| shared post editor |
Editor for posts shared from another user. Page: pages/_accid/sharedposteditor/_id/. |
| template editor |
Editor for design templates (not posts). Page: pages/_accid/templateeditor/. |
Misc
| Term |
What it means |
| MFA |
Multi-factor auth. Endpoints: /sendMFA, /MFAauthenticate. Likely SMS or email OTP. |
| welcome modal |
First-login modal. Endpoint: /auth/getDetailForWelcomeModal. Component: see modal-named files in components/. |
| AI generation |
Text and image generation features inside the editor. Powered by Gemini, Vertex AI, Stability AI, Leonardo AI. Keys live in polotno-editor/.env. See 08-integrations.md. |
| fallback path |
The most recent valid route the user visited, written by middleware/validUrl.js to localStorage.fallback-path. Used by error pages or 404 handlers (verify with the team — read sites are sparse). |
When you find a term that's not here
If you encounter a term in the code or in conversation that this glossary doesn't cover and which isn't self-evident from the code, add it here. Treat the glossary as living documentation; a future engineer's onboarding pain is paid down by every entry you add.