Identity & context inputs

One account, created once at hq.kariant.app, carries every role — buyer, partner, advertiser — across every Kariant surface. It contributes the sign-in identity and verified contact points, the roles held per surface, language and region defaults, and the security context (sessions, providers).

For buyers this means continuity: saved comparisons, shortlists, and chat threads follow them across sessions and devices. For partners it sets the currency context and runs your console, wallet, and every role from one login. At the agentic tier it is also the permission boundary: agents act strictly within what the account’s scopes allow.

The master profile at /profile updates in real time across the platform: professional identity (role, function, seniority), interests and followed categories, engagement history (views, compares, saves, chats), and communication preferences.

This is what makes the same search return different, better-fitting orders for a marketing lead and a CTO. For partners, profile completeness counts toward your badges (recognition only — actions never earn Koins), and your professional context personalizes your console. At Kariant AI, matching reads profile role and interests to weight intent; at Agentic AI, agents tailor conversation depth to the person they are talking to.

The organization record at /organization carries the company-level identity: the globally-unique @handle, industry, company size, region, billing currency (₹ India / $ Global), teams, and subsidiaries.

It powers B2B matching at the company level — recommendations weight what organizations of that industry, size, and region actually adopt, not just what one person clicked. For partners it sets billing region and contextual pricing, carries the verified identity behind listings, and scopes team access. At the agentic tier, agents reason about company-level fit before citing or contacting: an enterprise brief and a solo-founder brief produce different shortlists.

Your selected organization sets the context for your organization work. Changing accounts clears the previous account’s context while Kariant checks the new account’s access.

Shared context is included only after current access is checked for your selected organization or personal profile. It may be unavailable while you are offline or the check cannot finish. A share limited to products, services, or another area does not give you access to the whole organization.

Organization sharing currently offers read-only access to the whole organization profile and its entity records. Review the recipient and organization before confirming. Revoking a share does not remove other team permissions or copies already received. If confirmation is unavailable, check the current share list and contact support before making another change; refreshing the list does not retry the request. Do not reload or switch devices just to bypass an unresolved change.

Use Organization sharing to change who has shared access. Saving organization details or creating an organization does not add or restore sharing permissions from copied profile data. If an older share has no matching record, contact support for review rather than copying the old sharing list into a profile.

Organization membership is separate from a partner application. From the organization Teams console, its current owner may invite a verified Kariant account with or without a selected team. Invitations cannot transfer ownership or reactivate a suspended member. Acceptance checks the current account, invited email, owner, fresh application verification and exactly the invitation permissions reviewed. If the result is unclear, use Check invitation status on the original link; it reads current membership without accepting or sending again. Invitation creation saves its email queue record together, but queued is not delivered. Uncertain email sending needs support review before another invitation. A team Koins allowance is a policy limit, not a wallet credit.

The Teams console checks current server access and shows a paginated snapshot, not a live roster. Review the exact request before creating a team or invitation. If confirmation is lost, Check original request reads its retained status without posting or emailing again; an absent receipt does not prove it failed. Keep the same browser tab and its recovery reference, or contact support. Do not clear browser data to bypass an unresolved request. Refresh or return to the tab for current access; partial records and unknown IAM labels may need review. Organization membership still does not grant partner application approval.

The Kontext profile at /klick/kontext/profile is the declared context node: your ideal customer profile (target industries, sizes, regions, buyer roles), your offering context, the goals the AI should optimize for, and voice/tone constraints for generated content.

It is the single highest-leverage input a partner controls. It grounds lead-scoring reasons, the sales agent’s outreach drafts, intelligence prompts, and recommendation fit. At Basic it informs structured matching; at Kariant AI every AI run optimizes against it; at Agentic AI, agents read it before every run. Ten minutes spent sharpening your Kontext upgrades every AI surface you touch.