Account & Team Settings

Managing Account Settings

Settings is smaller than most people expect, and that is deliberate. Four pages, two scopes, and almost nothing that needs regular attention once it is right. Watch the walkthrough Prefer to watch? Ninety-three seconds on what follows you between workspaces, and the three things people keep looking for that are not here. The four pages The Settings navigation The navigation splits into two groups, and the split is the important part: ACCOUNT Profile — your name, your email, your password, and your company's invoice details. WORKSPACE Connections — the Amazon accounts feeding data in, and the per-brand sync toggles. MCP & API Keys — connecting AI tools to your data, and the log of what they asked. Aria in Slack — the Slack workspace link. Account vs workspace The Profile page states the rule directly: your account stays in sync across every workspace Account settings follow you. Your name, email and password are yours, wherever you are working. Change them once. Workspace settings belong to the workspace. Connections, MCP keys and the Slack link describe this workspace's data and integrations, not you. That distinction matters the moment you belong to more than one workspace — an agency, or a brand you consult for. Changing your password affects every one; disconnecting a brand affects one. What each page is actually for | Page | You go here to | |---|---| | Profile | change your name, password, or the details on your invoices | | Connections | add an Amazon account, fix a broken one, or stop a brand syncing | | MCP & API Keys | connect Claude or Cursor, issue a key, or audit what an AI asked | | Aria in Slack | connect or reconnect the Slack workspace | Connections is the one you will come back to Everything downstream reads the same data, so Connections is the first place to look when a number is wrong or missing: Set the filter to All, not Active. A brand switched off is invisible under Active — which is exactly the state you are usually trying to diagnose. See Turning Brand Sync On and Off. Read the last-synced time per source. SP and ADS sync separately, and a stale timestamp is a connection problem wearing the disguise of a data problem. Check which sources are connected. SP, ADS, Amazon DSP and AMC are four separate grants; having one does not imply the others. See Managing Your Connected Accounts. What is not in Settings Worth knowing so you stop looking: Users and permissions are not on this role's Settings. If you cannot see a page a colleague can, that is a role difference. See I Can't See a Menu Item Other People Can. Alert configuration lives with Alerts, not Settings. Rule configuration lives in Automations. The brand and marketplace picker is in the top bar on every screen, not in Settings. See Switching Brands and Choosing a Marketplace. The email field is read-only On Profile, Name is editable and Email is not. Your email is your identity for signing in, so changing it is not a self-service edit — contact support if it genuinely needs to change. See Getting Help from the TrackIQ Team. Password changes are self-service: New Password, Confirm Password, Update Password. Use something you do not reuse elsewhere. A sensible first-run pass Once, when you set up: 1. Profile — your name, a password you do not reuse. 2. Company information — so invoices carry the right legal entity and tax ID. See Company Profile. 3. Connections — every brand and every source, with the filter on All. 4. Aria in Slack — if your team works there. 5. MCP & API Keys — only if you are connecting an AI tool. Then leave it alone. Settings is not a screen that rewards fiddling. Related - Company Profile — the invoice identity block. - Managing Your Connected Accounts — the Connections page in full. - Turning Brand Sync On and Off — the toggle that stops data arriving. - The MCP Web Console — connecting AI tools. - Switching Brands and Choosing a Marketplace — the scope control that is not in Settings. - Company Profile — the invoice identity block on the same page.

Security and Data Protection

The short answer is yes: enterprise-grade encryption, your data is never shared with third parties, agency clients get isolated environments for each brand, and you maintain full ownership of your data at all times. The rest of this article is the part that is more useful than a reassurance — what you control, and where to look to verify it yourself. Watch the security walkthrough Prefer to watch? Seventy-two seconds on what you control, and where to verify it yourself. What TrackIQ can do with your Amazon account It reads. It does not sell, list, or message customers. Each connection is a standard Amazon authorisation: you sign in to Amazon, approve access, and are returned to TrackIQ. TrackIQ never receives your Amazon password — that exchange happens on Amazon's side, and what comes back is a revocable access token. Each source is authorised separately, and shows when it last synced Two properties of that arrangement are worth knowing: Access is separable. Seller, Advertising, DSP and AMC are four independent authorisations. You can grant advertising access without granting DSP. Access expires by design. Amazon issues time-limited tokens rather than a permanent key, and revoking access in Seller Central or the Advertising console cuts it immediately. You are never in a position where you cannot withdraw it. See Fixing a Broken or Expired Amazon Connection. Who inside your company can see what Access is enforced per role, and the enforcement is genuine rather than cosmetic. Sections you do not have access to are removed from the sidebar entirely, not greyed out. Navigating directly to the URL returns a 403 Access Denied page rather than the content — the restriction is on the server, not in the menu. Billing is a good example: a user without billing permission cannot reach Billing & Usage by any route, on any plan. Users and roles are managed under Users & Access, available on Starter and above. Multiple brands are separated Every reporting screen is scoped to the brand selected in the top bar, and agency clients get isolated environments for each brand. This is the property that matters most if you manage other people's businesses: one client's numbers do not appear in another client's view, and access can be granted per brand. AI access is the part worth checking This is where a security question actually earns its answer, because it is the newest surface and the least familiar. Aria works inside TrackIQ, on the brand you have selected, under your own permissions. It cannot see what you cannot see. MCP — connecting your own AI assistant, like Claude Desktop — has three properties worth stating explicitly: It is read-only. Nothing an assistant does through MCP can change a bid, pause a campaign, or alter your account. It is scoped to one brand, chosen on the consent screen when you connect. A connector approved for one brand cannot read another. Connecting a second brand is a separate, deliberate act. Every request is logged. Settings → MCP & API Keys → Call Logs records the question that was asked, how many tool calls it took, and when. Call Logs is a per-question audit trail of AI access That last one is the practical answer to “which AI tools have been talking to our data?” — you can read it rather than trust it. API keys are the one thing you must manage Everything above is enforced for you. API keys are the exception, because they are standing credentials that live wherever you put them. Issue one key per thing that uses it, never one shared key — revoking a shared key breaks everything at once, while a named key breaks only what you meant to break. Never paste a key into a chat, a ticket, or a shared document. Use environment variables or a secret store. Revoke rather than forget. Each brand's panel shows active and revoked counts, which is your audit trail. If you only use Claude Desktop, issue no keys at all. It self-registers through OAuth and needs none, which is the safest state available. See Installing TrackIQ MCP in Claude Desktop and Cursor. A short checklist Worth running once a quarter, and it takes about ten minutes: 1. Settings → Users & Access — does anyone here no longer work on this account? 2. MCP & API Keys — is every active key still in use? Revoke the rest. 3. Call Logs — does the AI access match tools you recognise? 4. Connections — is anything connected that you no longer need? The first and last catch the most common real-world exposure by a wide margin: access that outlived the reason it was granted. Related - The MCP Web Console — issuing and scoping AI access. - MCP Call Logs: Seeing What Your AI Tools Asked — the audit trail for AI queries. - Managing Account Settings — where the account controls live.

Company Profile

Company information is the least interesting screen in TrackIQ and one of the few worth getting right the first time, because it is what appears on things you send to other people. Watch the walkthrough Prefer to watch? Ninety-three seconds on legal name versus brand name, and why the billing email should not be a person. Where it is Settings → Profile, second section, below Account. Company information The card states its own purpose: Details that appear on invoices and reports across your workspace. Two audiences, then: your finance team, and anyone you send a report to. The fields | Field | What it is for | |---|---| | Legal Company Name | the entity on the invoice — not your trading or brand name | | Billing Address | street address for the invoice | | City | | | Postal Code | | | Country | a dropdown, and it drives tax treatment | | Tax ID | VAT number, EIN, ABN — whatever your jurisdiction uses (12-3456789 is the placeholder, not a value) | | Email for receiving invoices and billing notices | where billing mail goes | Save commits the section. Legal name, not brand name The most common mistake on this screen. Your brand is what customers see on Amazon. Your legal company name is what your accountant and the tax authority recognise. They are frequently different, and an invoice made out to the brand name can be rejected or need reissuing. If you are unsure, use the name on your company registration. The billing email is a separate address The email on the Account section above is your sign-in identity. This one is where invoices and billing notices are sent, and they should usually be different: Point it at finance or accounts payable, not at the person who happens to administer the tool. Use a shared mailbox, not an individual. People leave; accounts@ does not. Check it is monitored. A failed payment notice sitting in an unread inbox is how access gets interrupted. Tax ID and Country belong together The Country dropdown is not decoration. Between them, Country and Tax ID determine how your invoice is treated — whether tax is charged, and at what rate. Fill in the Tax ID if you have one. A registered business without its number on file can end up paying tax it could have accounted for itself. Set Country before you worry about the Tax ID format. The country establishes which identifier is expected. When to fill it in During setup, before your first invoice. Retroactive invoice corrections are a nuisance for everyone and often cannot be done at all for a closed period. When your company details change — a change of registered address, a new entity, a new tax registration. Before you send reports outside your own team, since these details also carry through to reports. This is not the billing screen Worth separating the two: Company information is your identity — who the invoice is made out to. Payment methods, plan and usage live in the billing area, which is a separate part of Settings and needs billing permission to reach. Changing your address here does not change your card, your plan, or when you are charged. A note on scope The Profile page's strapline reads "your account stays in sync across every workspace" — and the Company card sits on that page, described as applying "across your workspace". If you work across more than one workspace, check the company details on each rather than assuming the block you filled in yesterday applies here too. Related - Managing Account Settings — where this page sits. - How Revenue-Based Pricing Works — what you are being invoiced for. - Getting Help from the TrackIQ Team — if an invoice needs correcting.

Managing Multiple Brands

TrackIQ handles several brands in one workspace, and the model is simple once you see it: brands are separate everywhere except your login and your bill. Watch the walkthrough Prefer to watch? Ninety seconds on what is shared, what is not, and the partial-sync trap that looks like healthy data. Where brands live Settings → Connections → Brands & marketplaces. The connected brands panel Each brand is a row with: An Active toggle — whether its data syncs at all. Account name — the brand as TrackIQ knows it. Connected accounts — a count chip (1 SELLERS) that expands to the individual Amazon accounts beneath it. Each account underneath carries its own toggle, its seller ID, a last-synced time per source, and chips showing which grants are live — Connected SP, Connected ADS, Connected Amazon DSP, Connected AMC. Set the filter to All Show: All, Active or Inactive The SHOW control has three settings — All, Active, Inactive — and it defaults to Active, which hides the brands that are switched off. That is the wrong default for diagnosis, because a switched-off brand is precisely what you are usually looking for. Set it to All before concluding a brand is missing. Inactive is the quickest audit of the three: it lists only the brands currently not syncing, which is the answer to "what have we turned off and forgotten about". What is per-brand, and what is not | Scoped to a brand | Shared across the workspace | |---|---| | all reporting and analytics | your login and password | | campaigns, targets, keywords | your plan and invoice | | rank projects | company information | | alerts | the Slack workspace link | | automation rules | | | SQP tracked queries | | Two consequences worth internalising. A rule you built for Brand A does not touch Brand B. Multi-brand automation means building the rule per brand. And there is no cross-brand view. No combined dashboard, no "all brands" total. The two-level toggle The trap in this screen. Brand off — nothing for that brand syncs. Unambiguous. Brand on, one account off — partial data, which is far more confusing than none. The brand looks healthy at the top level while a whole seller account is silently absent from every number underneath. If a brand's figures look plausible but too low, expand it and check every account beneath it, not just the brand row. See Turning Brand Sync On and Off. Adding a brand Each brand is a separate Amazon authorisation, and each marketplace within it is separate again. Connect the Seller Partner account first, then Ads, then DSP and AMC if you have them. Four grants, not one. See How to Connect Your Amazon Accounts. Expect a first-sync delay. History arrives over the following hours, and rank tracking has no backfill at all — it starts the day you create a project. See Rank Data Shows Blank. Working across several brands Practical habits from the shape of the model: Name the scope in every report. Two people comparing figures read at different brands is the most common false alarm there is. Build rules brand by brand, and label them. A rule name that includes the brand saves confusion in the Change Log. Pin a Slack channel per brand. Aria in Slack keeps a brand pin per channel — Brand A in #marketing, Brand B in #ops — which is the cleanest way to keep two brands' numbers from being read as one. See Turning Brand Sync On and Off and Chatting With Aria in Slack. Scope MCP keys to one brand. A per-brand API key cannot read a brand it was not issued for, which is both tidier and safer than one key that can see everything. See The MCP Web Console. What this does not cover Users and permissions per brand. Whether a colleague can be given one brand and not another is a role question, and Users & Access is not available on every role. See I Can't See a Menu Item Other People Can. Billing per brand. The plan and invoice belong to the workspace, not the brand. See How Revenue-Based Pricing Works. Related - Switching Brands and Choosing a Marketplace — the picker. - Marketplaces and Currency — the level below brand. - Turning Brand Sync On and Off — the toggle in detail. - Managing Your Connected Accounts — the Connections page.

Marketplaces and Currency

A marketplace is not just a filter. It is a separate Amazon account, reporting in its own currency, with its own listings, its own competitors and its own search behaviour — and TrackIQ keeps them separate for good reason. Watch the walkthrough Prefer to watch? Ninety-nine seconds on why there is no combined total, and which figures survive a border. Marketplace sits below brand The marketplace section of the picker The top-bar picker has the brand at the top and a MARKETPLACE section beneath it, each entry showing the country name, its two-letter code, and a checkmark on the active one. So the hierarchy is: Workspace → Brand → Marketplace → the data you are looking at. A brand's marketplace list is its own, which is why the list changes when you switch brand. See Switching Brands and Choosing a Marketplace. Each marketplace carries its own currency This is the fact that matters most for reporting. Every marketplace connection records a currency alongside its country and account type — a US connection reports in USD, a Mexican one in MXN, a UK one in GBP, and so on. Amazon reports each marketplace in local currency, and TrackIQ reports what Amazon reports. Three consequences: The currency symbol on screen follows the marketplace, not a workspace preference. Figures from two marketplaces are in different units. A spend of 20,000 means something very different in two currencies. There is no conversion and no combined total. TrackIQ does not present a cross-marketplace sum, because summing unconverted currencies would be wrong and converting them needs a rate and a date that are your decision, not the tool's. Never add across marketplaces The single most damaging habit available on this screen. Adding USD to MXN produces a number that is not money. It looks like a total and means nothing. Averaging ACoS across marketplaces is equally wrong. A ratio of two currencies is dimensionless, so ACoS is comparable — but an unweighted average of two ACoS figures is not a portfolio ACoS. Weight by spend, in a common currency, or do not do it. If you need a group figure, convert each marketplace at a stated rate and date, do the arithmetic outside TrackIQ, and say what rate you used. That is a finance exercise, not a reporting one. What is comparable across marketplaces Ratios and rates travel; absolute money does not. | Comparable | Not comparable | |---|---| | ACoS, TACoS, ROAS | spend, sales, CPC | | CTR, conversion rate | AOV | | impression / click / cart / purchase share | search volume | | rank and visibility | units, if pack sizes differ | Even the comparable ones deserve caution. A 30% ACoS in a mature marketplace and a 30% ACoS in one you launched last quarter are the same number describing different situations. Each marketplace is a separate connection A common misunderstanding when a marketplace does not appear. Authorising your US seller account does not grant Canada or Mexico. Each is its own authorisation, even within the same Amazon regional group. Each marketplace also has its own Ads, DSP and AMC grants, so a marketplace can be present with SP data and missing its advertising data entirely. Check the source chips on the account card in Connections. See Managing Your Connected Accounts. Account type comes with the connection too Each marketplace connection also records whether it is a Seller, Vendor or KDP account, and that changes what is reported — sellers identify products by SKU, vendors by ASIN. So one brand can hold both a Seller and a Vendor connection for the same country, and they will not look alike. See Seller vs Vendor Accounts: What Changes in TrackIQ. Working across marketplaces sensibly Do the work marketplace by marketplace. Rules, budgets, keywords and rank projects all belong to one. Compare on rates, report in local currency, and state the marketplace next to every figure. Expect different search behaviour. The same product sells on different queries in different countries, so SQP and Rank Tracker findings do not transfer. Re-run the analysis rather than assuming. Watch inventory separately. Stock is held per marketplace, and a healthy US position tells you nothing about the UK. Related - Switching Brands and Choosing a Marketplace — the control. - Managing Multiple Brands — the level above. - Seller vs Vendor Accounts: What Changes in TrackIQ — the other axis of a connection. - Why Don't My Numbers Match Seller Central? — when a single marketplace disagrees. - Narrowing Fifteen Ideas to Seven — checking demand across marketplaces before committing.