Create an AdAce Ads workspace: email confirmation and first checks

Registration, invitation and ownership

Creating a new account and signing into an existing account have different outcomes. In public registration mode, submitting the email form starts confirmation for an eligible new address. A new user and their own workspace are created only after confirmation succeeds; that user becomes its owner. Existing addresses follow sign-in and do not receive another workspace. A normal sign-in request for an unknown address does not create a workspace. A deployment can instead require an invitation or disable registration; a private beta can also restrict eligible email addresses.

An invitation gives permission to join the named workspace, but it does not prove ownership of the email address. Confirm the invited address in the browser that requested the email, then explicitly accept the invitation. An invited user joins the existing workspace rather than automatically receiving a separate agency workspace. If the invitation has expired or was withdrawn, ask the workspace administrator for a replacement.

For example, an agency owner may create one workspace and then add two clients, North Store and South Service. Each client should have its own account assignments and team access. A manager assigned to North Store should verify that North Store is visible before starting work. Email confirmation establishes application access; Google or Meta must separately authorize advertising data access through their own consent flow.

The application applies workspace and client access checks to its pages, API and AI tools. Treat this as an implemented access-control design, not a promise that configuration can never be wrong. Validate assignments with the teammate's account, use synthetic records for an initial rehearsal and investigate unexpected visibility before adding client data. A setup checklist provides navigation, but completing it does not certify provider readiness.

A useful first workspace

• Keep ownership, client context and responsibilities explicit from the first session instead of sharing an agency login.
• Use invitations to add teammates to the intended workspace and client assignments to define their working scope.
• Separate a successful email confirmation from account discovery, imported campaigns and verified advertising data.

Create and verify access

1. Open the application, enter your email in the form offered for your deployment and request the confirmation message. Use an address you can access; check its spelling before submitting. For team access, start from the invitation.
2. Open the confirmation message in the same browser and explicitly confirm the request. Merely opening a link may display a confirmation screen without completing sign-in.
3. Check the workspace name and your role. If joining a team, finish invitation acceptance and confirm that you are in the intended workspace.
4. Review account security. A newly registered account can start without a password; use the initial-password action if required and enable the second factor before privileged workflows.
5. Add one client, assign the appropriate teammate and verify visibility. Then continue with the setup checklist and a separately authorized provider connection.

Resolve confirmation and access problems

Sources and further reading

• AdAce Ads: setup checklist
• AdAce Ads: clients and assignments
• AdAce Ads: team roles