Request an organization account or create the first administrator
Public applicants use /request-account, choose login details, and verify the email address. Pending applicants can use /resend-verification to replace an expired or missing verification email. On a completely empty private installation, /setup creates the permanent God Admin and closes after the first user exists.
Complete or skip onboarding steps
Review organization identity, mail connections, enabled products, delivery defaults, and evidence. Optional steps can be skipped without losing access to them later.
Invite the organization team
The primary administrator can invite seats, assign reporting managers, and grant BRANDED, TEXTED, Inbox, Support, and report permissions. Invitations contain a one-time activation link.
Connect and verify the mailbox
Add SMTP for sending and IMAP for synchronization. Use OAuth or a provider-generated app password when required.
Authorize the mailbox through Google and begin the INBOX copy.
Select a Microsoft account and grant mailbox access.
Enter the mailbox address and provider-generated app password.
Enter SMTP and IMAP host, port, security, username, and password.
Confirm SPF, DKIM, and DMARC
Use provider DKIM when aligned. For a custom domain without signing, publish the single BRANDED public-key TXT record and verify it once.
Add controlled contacts and permission evidence
Begin with addresses and numbers you control. Record permission source, purpose, date, and supporting evidence. Suppressions always take priority.
[email protected]Permission recorded[email protected]Permission recordedSend one ordinary email
Send to an address you own. Confirm SMTP acceptance, received DKIM results, Sent-folder append, raw EML, and evidence events.
Open tracking, browser view, read receipt, delivery notifications, and unsubscribe controls.
Add files that will be preserved with the sent-message evidence.
Queue a two-recipient BRANDED campaign
Run preflight, confirm recipient permission, inspect the queue, and review final outcomes before increasing volume.
Pair the Android companion
Create a one-time token, enter the public server URL and token on the Android device, and confirm a recent heartbeat.
PAIR-EXAMPLE-7F3A-91C2Dummy token — never use this valuePreserve and extract email addresses
Open Email Extractor, paste copied text or upload mixed source files. Review the preserved source grid, unique results, source contexts, TXT/CSV exports, and forensic reports. A verified SMTP connection can email a selected export as an attachment.
Create the S!CRIBED! publication and review two drafts
Open Organization → S!CRIBED! Publishing. Choose the organization slug and publication title, then review the two draft articles. Select a theme and hero image, verify social metadata and iframe code, and publish only after the public analytics notice and retention settings are correct.
Create organization API and OAuth credentials
Open Organization → API integrations. IPinfo requires an access token and selected product; Twilio requires the Account SID plus a dedicated API Key SID and secret, or the Auth Token fallback. Cloudflare uses a zone-restricted token. Google and Microsoft contact sync use organization-owned OAuth web applications with the exact redirect URLs shown on screen.
Verify SMTP, DKIM, SPF, and DMARC
Open the domain page for the connected sending account. BRANDED can generate and apply a managed DKIM signature. Publish the SPF mechanisms supplied by the actual SMTP provider, start DMARC in monitoring mode, and use a scoped Cloudflare token only when automatic DNS publishing is desired.
Import, discover, synchronize, and export contacts
Import CSV addresses, extract correspondents from synchronized mail, authorize and synchronize Google People or Microsoft Graph contacts with the provider contact-read permission, and download the complete organization contact CSV. Never remove a suppression without documented renewed permission.
Trace observations to the original message
Open Evidence → Tracking Pixel Statistics. Review the token’s ordinary email or campaign origin, recipient, timestamps, IP, user agent, referrer, and event metadata. Treat an image request as a technical observation—not proof of human reading.
Publish the company and employee biography directory
Open L!INKED!, choose a page owner and one of five premium templates, then add biography blocks, social destinations, tracked links, media, allowed embeds, contact details, comments, and reviews. Publish only after the preview reflects the intended public identity.
Review the evidence vault
Confirm status, SMTP response, raw EML hash, DKIM selector, evidence-chain integrity, and generated reports. Tracking requests are technical observations.
Submission timestamp, server response, recipient, and connection details.
RecordedTechnical pixel event with timestamp, network, and user-agent information.
ObservedOriginal MIME structure, headers, HTML, text, and attachment metadata.
PreservedDownload a themed BRANDED or TEXTED PDF with a cover page, executive summary, recipient ledger, queue diagnostics, transport evidence, hashes, event timeline, and technical appendices.
Publish the organization’s short-link hostname
Company Admin or God Admin opens T!RACKED! → Setup, publishes joey.camp or another company-controlled hostname to the BRANDED service, verifies it, and creates the first redirect or pixel. Choose the short-code format, notification recipients, and every-observation, hourly, daily, or weekly email/PDF schedule.
Use focused evidence tools without mixing their records
Install or import a complete signature
Open Settings, locate Signature import, then install the bundled B!RANDED + T!EXTED identity or upload an HTML, HTM, or TXT signature file. Existing signature versions remain preserved.
Private professional conversations with explicit identity controls
C!HATTED! profiles are private by default and there is no complete public directory. Exact username search reveals only the information each person authorizes. External participants remain visibly labeled, one-time invitations expire or become invalid after use, and senders may remove their own messages at any time while immutable forensic records preserve the original content and deletion event.
Employees see conversations in which they participate. Company senior administrators may review employee-related conversations, diagnostics, and reports under the existing oversight model. Verification marks classify identity and do not endorse a person’s statements; company flair is administered by the applicable company.