Team & Settings

This guide covers the administrative side of Lynkist: your Settings area. It's where you manage who you are, who's on your team, and how the workspace connects to the outside world. (The WhatsApp connection itself has its own guide — see WhatsApp Setup.)

Profile

Settings → Profile is your personal account: first name, last name, and your contact details. This is per-user — each teammate manages their own profile.

Organization

Settings → Organization is the workspace itself, shared by everyone:

• Company name — your business name across the app.
• Workspace URL — the slug your workspace lives at.
• Timezone — the workspace's default timezone.

Why timezone matters

Lynkist stores all timestamps in UTC internally, but displays and schedules them in the effective timezone. Your personal setting takes priority where available, falling back to the workspace timezone. Get this right before scheduling campaigns — a wrong timezone is the usual reason a "9am" send goes out at the wrong hour.

Team — invite and manage people

Settings → Team is where you build your team:

• Team Members — everyone with access, and their role.
• Pending Invites — people invited who haven't accepted yet.
• Roles & Permissions — what each role can do.

Inviting a teammate

Add their email address, choose a role, and send the invite. They'll get an email to join. Until they accept, they sit under Pending Invites. You can change role on an existing member at any time.

Security

Settings → Security covers your account's protection — changing your password and related account-safety controls. For Lynkist's platform-level security posture (tenant isolation, encryption, audit logging), see the Security page.

Webhooks — get events into your own systems

Settings → Webhooks lets you receive a callback whenever something happens in your workspace (message delivered, reply received, and so on) so you can sync to your own systems. This is the build-your-own counterpart to Integrations.

Adding an endpoint

1. Click Add Endpoint.
2. Enter your endpoint URL (must be HTTPS and publicly reachable).
3. Add an optional description and any custom headers you need.
4. Save — your endpoint appears under Active Endpoints with a health status: Healthy, Degraded, or Disabled.

Verifying payloads are really from Lynkist

Every delivery is signed. You get a signing secret at creation; use it to verify the X-Lynkist-Signature header (an HMAC-SHA256 signature over the payload), alongside the X-Lynkist-Timestamp header to reject replays. You can rotate the secret at any time.

Delivery rules to design for

• Respond with a 2xx within 5 seconds, or the delivery counts as failed.
• Failed deliveries retry on a backoff schedule: 1m, 5m, 30m, 2h, 6h.
• After 20 consecutive failures, the endpoint auto-disables — so monitor health and keep your receiver up.

Next steps