Operate BRANDED by seeing it first.

Dashboard navigation

The fixed main menu groups BRANDED into Overview, Send, Inbox, Contacts, Evidence, and Settings. The illustration follows the current BRANDED 9 navigation and component theme.

Request, verify, onboard, and upgrade

New applicants create their own login details, verify the email address, and enter a guided organization onboarding flow. Optional mail, product, and default-setting steps can be skipped and revisited later. Trial records remain preserved if access becomes restricted or the organization upgrades.

Assign seats, roles, and product access

The primary organization administrator can invite up to the organization seat limit, assign a reporting manager, and enable only the tools each seat needs. A seat can be limited to BRANDED, TEXTED, the Un-Ordinary Inbox, Support, or Evidence reports.

Use the organization logo and attachment library

Organization administrators upload a logo and designate standard-email and campaign accounts. Attachments from outbound and synchronized inbound messages are stored inside the organization library. Images and PDFs display beside message and campaign details.

Connect a mail provider

SMTP sends mail. IMAP copies mailbox folders and can append the final message to Sent. Verify both transports before using the account. Provider-managed accounts may use OAuth; other providers may require a generated app password.

DKIM and domain health

BRANDED checks whether the selected provider already applies aligned DKIM. A custom domain without signing can generate a BRANDED-managed key, publish the public TXT record, and verify DNS once.

Create a controlled campaign

Choose the sending connection, add recipients with documented permission, provide HTML or plaintext (or both), and run preflight before queueing.

Rendered email and source code

This dummy email is rendered as actual HTML beside escaped source code. Email bodies should favor table layouts and inline CSS for compatibility.

  

    

      Your July account update
    
  
  

    

      Hello Alex,
      
        Open dummy dashboard
      
    
  

Synchronize and compose ordinary mail

Ordinary email uses the same selected connection, queue controls, DKIM path, raw EML preservation, Sent-folder append, and evidence recording as campaign email.

Queue control

Evidence and reports

Review the raw-message hash, Message-ID, SMTP response, DKIM selector, recipient outcome, and observed tracking requests. An open request is a technical observation and not definitive proof that a human read the message.

Pair and operate an Android device

Administer organizations and user accounts

The Administration Center separates the permanent God Admin from delegated site administrators. God Administration can review every organization and hierarchy. Delegated site administrators can perform assigned global operations but cannot inspect or modify the God Admin account or its home organization. It controls organization state, sending pauses, capacity limits, user email addresses, account suspension, and administrator-reviewed password resets.

Contact the administrator and continue in-account

Contact administrator opens a structured ticket form. Organization support can be assigned internally or escalated to platform administration. Conversation PDFs remain available to the requester and administrators, and are generated on demand, when closed, or after thirty minutes of inactivity. The request appears in the user's Support Center and the administrator queue, and the conversation refreshes automatically while both participants are signed in. The form discloses requester-side diagnostic collection; only platform administrators can review requester IP, browser, Cloudflare and request metadata for troubleshooting.

Email Extractor evidence workspace

Every signed-in seat can paste source text or upload supported PDF, Word, Excel, PowerPoint, OpenDocument, CSV, EML, HTML, JSON, and text-based files. Sources, extracted text, addresses, exports, hashes, and forensic reports remain stored by organization and hierarchy.

Obtain and test IP, carrier, and DNS credentials

Authenticate the domain used by the SMTP connection

BRANDED can sign mail with a managed DKIM key after the public TXT record is verified. SPF must authorize the servers that really transmit the mail, and DMARC evaluates alignment. These DNS records do not turn the BRANDED web server into a public mail-transfer agent; the selected SMTP account still performs submission and delivery.

1. Connect and verify the SMTP account.
2. Open DKIM and domain for that connection.
3. Publish the generated DKIM TXT record.
4. Add the exact SPF mechanisms provided by the SMTP service.
5. Begin DMARC with reporting, review results, and strengthen policy deliberately.

Import, find, synchronize, export, and safely restore

The inbox composer can search saved email contacts and add a new one in place. Connected-account contact sync can always extract senders and recipients from synchronized messages. Google and Microsoft address-book sync additionally requires the organization to configure its OAuth web application under API integrations, authorize the matching mail connection, and grant the provider’s contact-read scope. Generic IMAP does not expose an address book.

Suppression restoration is restricted to organization administrators and requires renewed permission, a reason, and evidence. The restoration creates a fresh granted-consent record and an administrative audit entry.

Trace every sent pixel to its origin

Evidence → Tracking Pixel Statistics lists each outgoing message that carried an observation token. Open the item to see all open and tracked-link events, including timestamps, available IP addresses, browser or proxy metadata, and links to the original message and campaign.

Preserve exported messages, intelligence, and support images

Publish a branded L!ETTERED! double-opt-in signup page

Organization administrators choose the public URL slug, headline, description, keywords, colors, consent text, privacy and terms links, and whether names are collected. The page publishes Open Graph, X/Twitter, Schema.org, canonical, logo, social-card, and oEmbed metadata.

For verification, abuse prevention, and organization analytics, signup events preserve the available IP address, private hash, browser information, referrer, country indicator, campaign parameters, event type, and timestamp. The public form discloses this technical metadata collection.

Publish articles with safe HTML, social metadata, embeds, and analytics

Each organization can create one S!CRIBED! publication only after an organization administrator chooses a unique slug and title. Public pages use /blog/organization-slug and individual articles use /blog/organization-slug/article-slug.

Turn a S!CRIBED! article into a B!RANDED! campaign

A published article offers “Send newsletter.” The composer builds a themed introduction, inserts the sanitized article HTML, adds a direct article button, and combines selected active contacts, confirmed subscribers, pasted recipients, and CSV uploads. Addresses are deduplicated, suppressions are enforced, permission must be attested, and open/link/unsubscribe/receipt controls remain explicit.

Create company and employee pages that are more than a list of links

Open L!INKED! from the main navigation. Employees can manage their own page; organization administrators can create company pages and authorized employee pages. Every page remains organization-bound.

Connect a company hostname and create a private B!RANDED! entrance

Company Admin and God Admin accounts may connect unlimited organization-controlled hostnames such as branded.example.com. The company hostname changes only the entry identity and theme. It does not replace, redirect, or weaken joseph.anthony.camp, which remains the definitive canonical site and login for the complete platform.

Cloudflare in the same account

1. Open Cloudflare Zero Trust and the named tunnel already serving the canonical site.
2. Add the company hostname as another Published application.
3. Use the same local service shown in the Company Domains setup screen.
4. Save the route and return to B!RANDED! for verification.

Cloudflare for SaaS or another registrar

1. God Admin configures the platform fallback origin and optional encrypted Cloudflare API token.
2. Create the exact hostname as a Cloudflare Custom Hostname, manually or from B!RANDED!.
3. Publish the ownership and certificate-validation records Cloudflare displays.
4. Point the company hostname to the platform CNAME target displayed in B!RANDED!.
5. Wait for both hostname and SSL status to become active, then run the B!RANDED! health check.

Safe termination

Open the hostname, choose Terminate, read both warnings, type the full hostname, and confirm. Termination stops company-host access but preserves the company, user accounts, chat metadata, theme history, health checks, login outcomes, and immutable forensic chain. DNS and provider cleanup instructions remain visible after termination, and God Admin or the Company Admin may reconnect the hostname later.

Connect a domain, create a compact route, and preserve its observations

God Admin and Company Admin accounts can connect one or many organization-controlled hostnames. Joseph Anthony Camp can begin with joey.camp; another company can use its own apex domain or a dedicated subdomain. Open T!RACKED! → Domain setup for the current Cloudflare Tunnel and reverse-proxy instructions.

T!RACKED! does not perform canvas, audio, font, or cross-site fingerprinting. Administrators must use it only with the disclosures, consent, lawful basis, and platform rules applicable to the deployment.

Private professional conversations with explicit identity controls

C!HATTED! profiles are private by default and there is no public or cross-company directory. Internal employees receive a directory containing only active C!HATTED!-enabled coworkers in their own company; external accounts receive no company directory. Exact username search and shared-conversation discovery remain bounded. 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 and cannot see an external contact’s other chats. Company senior oversight is limited to internal-only company conversations unless the administrator is personally a participant. Verification marks classify identity and do not endorse a person’s statements. A company may assign its own verification and flair to employees and to external contacts who accepted that company’s invitation, without gaining access to unrelated communications.

Read all C!HATTED! rules Create standalone C!HATTED! access

Invoices, payroll, contracts, products, subscriptions, and provider-connected settlement

B!ANKED! is visible only to the organization’s Company Admin and specifically assigned B!ANKED! seats. God Admin receives read-only diagnostic oversight and cannot create, approve, settle, cancel, or edit financial records.

• Create company-specific invoices with unlimited line items, custom taxes, VAT, processing fees, terms, notes, due dates, products, services, contracts, subscriptions, payroll, purchases, contractor payments, and receipts.
• Record ACH, credit, debit, electronic transfer, SEPA, wire, and EFT transactions through sandbox, manual settlement, or company-approved hosted providers.
• Verify bank-account relationships through sandbox, manual evidence, or an approved verification provider. Never enter raw card numbers, CVV, online-banking passwords, or reusable bank credentials.
• Store W-2, 1099, VAT, tax, contract, and bank-verification files in the company database with encryption, hashes, access control, and immutable events.

Draft invoice workflow: invoices remain fully editable—including party, dates, terms, notes, unlimited line items, prices, discounts, taxes, VAT, and fees—until an authorized seated user chooses Approve final invoice + submit. Submission locks those fields and preserves the final version in the event trail.

Product lifecycle: use Edit from either B!ANKED! Products or S!HOPPED! Products to change SKU, description, pricing type, price, tax, VAT, processing fee, inventory, publication, or active status. Deactivation preserves historical orders and invoices.

Public products and services with B!ANKED!-connected checkout

S!HOPPED! is visible only to the Company Admin and assigned S!HOPPED! seats. It publishes approved B!ANKED! products into a responsive public store with carts, customer accounts, orders, invoices, payment status, receipts, fulfillment, and support.

• Create products or import catalog data from CSV, JSON, Shopify-style exports, and supported APIs.
• Control price, inventory, subscription interval, taxes, VAT, processing fees, visibility, terms, and product description.
• Keep customer identities and contractor/payee portals separate from company B!RANDED! administration accounts.
• Every successful store order creates linked B!ANKED! invoice, transaction, receipt, notification, and immutable evidence records.

S!HOPPED! seats can create and edit products directly from storefront administration. Shared product changes update the B!ANKED! catalog without granting access to payroll, contracts, or other financial administration.

Create, publish, and operate an isolated company tool from any compatible HTTPS API

The guided composer explains endpoints, methods, fields, headers, encrypted secrets, request bodies, response mapping, testing, assignments, direct company publication, panic controls, and health checks for a first-time API developer.

Tools can submit structured fields or bounded file uploads and can present JSON, text, research, images, art, audio, video, PDFs, documents, and other binary results. Optional HTML, CSS, and JavaScript remain inside an opaque no-network browser sandbox and never execute in the B!RANDED! server process.

1. Create the organization-scoped tool shell and conflict-safe slug.
2. Define bounded inputs, headers, response mappings, and encrypted secrets.
3. Build declarative requests and an optional sandboxed presentation.
4. Test the draft and assign company roles or individual memberships.
5. Publish the immutable version directly as an authorized company C!ALLED! administrator.
6. Use Internal Tools for private employee tools and public/external tools; public tools also receive a clickable external URL.
7. Monitor runs, scheduled health checks, forensic events, and tool-only panic controls.

Start with the exact failing layer