We’re upgrading our email infrastructure — for immediate response, email andrewjgaber@gmail.com meanwhile.
Skip to main content
Products:PixelProofEntryProofTariffWatch|Free tools:Meta Pixel DebuggerHTS Code LookupCPSC Penalty CalculatorSchema Markup GeneratorRobots.txt CheckerPrivacy Policy GeneratorCookie Consent Checker|Help|About|RoadmapChangelog

Help center · Account & billing

Adding a teammate to your Digital Empire account

By Andy Gaber · Published August 20, 2026 · Last updated August 20, 2026

Digital Empire products are single-seat by default at the current pricing tiers. If you want a teammate to see the same scans, receive the same alerts, or file a comment letter on your behalf, you have two options today and a third option landing in the M2 window. This guide walks all three.

Option 1: share an alert-destination webhook

The fastest way to bring a teammate into the loop, with no account changes, is to add a Slack channel or Zapier webhook as an alert destination on the PixelProof integrations page at /meta-monitor/integrations. Any teammate in that Slack channel or watching that Zapier zap will see every pixel-break alert PixelProof fires, in real time, without needing their own login. The same works for EntryProof status alerts via the account-page email-forwarding field.

This is the recommended path for two-to-five-person shops where one person owns the account and everyone else just needs visibility. It is documented under the Web Pixels API sandbox on shopify.dev as an equivalent "team notification" pattern -- Shopify itself uses shared Slack webhooks for its own team broadcasting rather than provisioning per-seat identities where the shared visibility is all you need.

Option 2: share the account credentials

If a teammate needs to actively edit the account (add a store, change alert destinations, download exports), the current-tier workaround is to share the account email and login. This is not a violation of the terms of service for a single organization -- shared logins between employees of the same company are permitted per the language in the California Attorney General's CCPA enforcement page at oag.ca.gov and standard shared-workspace commercial practice.

The practical caveats: password-reset emails and Stripe billing notices go only to the account email, so any teammate with edit access should either use a shared inbox (help@yourcompany.com) or route a copy of the account inbox to Slack. Two-factor authentication, when we ship it, will replace this workaround with real per-teammate identity.

Option 3: the M2 Agency seat plan (coming)

The Agency plan on the PixelProof pricing page at /meta-monitor/pricing is scoped to include real seat-based team access: one billing owner, up to five teammate seats, each with their own login, their own email address for alerts, and permission tiers (viewer, editor, admin). Agency plan customers also get API access via the OpenAPI docs at /docs/api.

The Agency plan is scheduled for M2 (October 2026) and is one of the top three items on the roadmap posted at /meta-monitor/roadmap. Founding Trio customers are grandfathered into a locked-in early-adopter Agency seat price when it launches, per the founding-cohort commitment at /founding-trio. The seat mechanics are modeled on the widely used pattern documented on the Shopify Partners team-permissions reference at shopify.dev -- one billing owner, per-seat permission scopes, invitations sent by email with a one-time-use accept link.

What data teammates can currently see

Any teammate with access to the account email has full read and write on that email's scans, stores, alert destinations, and billing. This matches the current pre-Agency-tier trust boundary: your account email is the single source of identity, and anyone with mailbox access has account access. We do not currently offer read-only or view-only teammate access; that requirement is the primary driver of the M2 Agency plan build.

How to prepare for the M2 Agency migration

Two things you can do now to make the eventual migration painless: (1) start using a shared team inbox (help@yourcompany.com) instead of a personal address as the account email, so the account identity is not tied to a single person; and (2) begin using the account page at /meta-monitor/account to record which teammates are effectively editors versus viewers, in the plain-text notes field, so the seat-provisioning process at Agency-plan launch can be scripted from your existing arrangement rather than started from scratch.

Was this helpful?

Yes / No

Related articles

FAQ

Can I add a teammate today at the current-tier pricing? Not with a separate login, but yes with alert-sharing or shared credentials. See Options 1 and 2 above.

How many seats does the Agency plan include? Five teammate seats plus one billing owner, per the tier posted on the PixelProof pricing page at /meta-monitor/pricing. More can be added at a per-seat rate.

What permission tiers will the Agency plan support? Viewer (read-only on scans and alerts), Editor (add or remove stores, edit alert destinations), Admin (billing plus everything Editor can do). One billing owner cannot be demoted from Admin.

Will Agency seats work across PixelProof, EntryProof, and TariffWatch? Yes. The Agency plan is portfolio-wide; a seat granted at the Agency level has cross-product access, subject to the underlying product's own permission checks.

Still stuck? Email hello@citationsafe.com or hello@argushq.ai.

Still stuck?

Email hello@citationsafe.com or hello@argushq.ai.

Digital Empire builds compliance tools for regulated verticals — pharma, consumer products, metals.

Also from Digital Empire

Bundle deal: all 3 for $299/yr (5 founding spots). Founding Trio → | All pricing
PixelProofMeta Pixel monitoring for ShopifyEntryProofCPSC eFiling readiness checkerTariffWatchSection 232 exposure checker

Popular free tools & roundups

Free Meta Pixel DebuggerFree HTS Code Lookup (§232)Free CPSC Penalty CalculatorBest Shopify pixel monitors 2026Best CPSC eFiling tools 2026Best Section 232 tools 2026Help centerAll free toolsAll productsReferral programStatus