Settings

The Settings page is the control room for your account and your workspace. It is where you do the housekeeping that keeps everything else running: add or remove the people on your team and decide what each of them can do, manage the secret keys your site and your tools use, list the websites you track, choose your plan and handle billing, set how long your data is kept, and connect leadmaps to other tools you use. You will not visit Settings every day, but when you need to add a colleague, swap a key, or change your plan, this is the one place it all lives.

Think of it like the settings on your phone. Most of the time you are using apps, not poking around in settings. But when you need to add a new account, change who can see what, or manage your storage, you open settings, make the change, and get back to work. The Settings page is that same back room for your leadmaps workspace.

A “workspace” is your whole account in leadmaps: your team, your websites, your plan, and your data all live inside it. Most of what you set here applies to the entire workspace, so a change you make affects everyone on your team, which is exactly why some of these controls are limited to certain roles.

What you see

Settings is organized into clear sections, each for one kind of housekeeping.

Team members. The list of people who can sign in to your workspace, each with a role. A role decides what someone is allowed to do, for example an admin who can change billing and invite others, a member who can view and work with the data, or a view only role for someone who should look but not change anything. You can invite new people, change someone’s role, and remove people who have left.
API keys. The secret keys that connect your site and your tools to leadmaps. There are two kinds, and it helps to know the difference. One kind lets your website send data in (it goes in the tracking snippet on your pages). The other kind lets tools read your data out (for reports, exports, or other software you connect). Each key is shown with a name and when it was created, and you can create new keys or remove ones you no longer recognize.
Websites. The list of sites you track in this workspace. Each site is one website you collect data for. You add a site here to start tracking it, and each site can have its own key and appear as a choice in reports that let you focus on one site.
Plan and billing. Your current plan, what it includes, and your billing details. This is where you see your limits, upgrade or change plan, and manage payment. When you outgrow the free limits, this is where you move up.
Data retention. How long leadmaps keeps your data before it is automatically removed. You choose the period that fits your needs and any rules you must follow, and older data beyond that period is cleaned up for you.
Connections. Links between leadmaps and other tools you use, so your data can flow where you need it. You add or remove a connection here.

An “API key” is just a secret password for software, not for a person. A person signs in with their own login. A key is what a piece of software uses to prove it is allowed to send or read data. Because a key is a password, you keep it private and replace it if it ever leaks.

How to read it

Settings is less about reading numbers and more about knowing who can do what, and which keys and sites are in play.

Here is a worked example. Say a new colleague joins and will be running your reports, and you also notice an old API key you are not sure about. You open Settings and see:

Team members: 3 people. You, an admin. One member. One view only.
API keys: two keys. One named “website” created months ago. One named “old-export-test” you do not recognize.
Websites: two sites, your main site and your blog.
Plan: Free, with its limits shown.

What do you do with this? First, the new colleague needs to work with the data but should not be changing billing, so you invite them as a member, not an admin. Roles are about least surprise: give each person exactly the access their job needs and no more, so a mistake or a lost laptop cannot do damage beyond that person’s role. Second, that “old-export-test” key you do not recognize is a loose end. A key you cannot account for is a key that might be in the wrong hands, so you remove it. If some tool was quietly using it, that tool will stop working and you will find out which one, which is far safer than leaving an unknown key alive. Reading Settings well is mostly this: making sure every person and every key is one you can explain.

One thing to keep in mind: some of these controls change things for your whole team and your billing, so they are usually limited to admins. If you cannot see or change a section, your role may not include it, and a workspace admin can either make the change or adjust your role.

Customize it

Each section is a control. Here is what you can change and when to use it.

Invite or remove a teammate, and set their role. Add a person by inviting them, choose the role that matches what they should be allowed to do, and remove people who leave. Invite someone as a member when they need to work with the data day to day. Choose view only for a stakeholder who should see reports but never change settings. Reserve admin for the few people who should manage billing, keys, and other people. Always give the smallest role that lets someone do their job, and remove access promptly when someone leaves.
Create or remove an API key. Make a new key when you set up a new website or connect a new tool, and remove a key the moment you suspect it has leaked or you no longer need it. Name each key for where it is used (for example “main-site” or “looker-export”) so you can tell at a glance what would break if you removed it. Treat keys like passwords: private, named, and replaced when in doubt.
Add a website. Add a site when you want to start tracking a new website in this workspace. Once added, put its key in that site’s tracking snippet, and the site becomes a choice you can focus on in reports that support picking one site.
Change plan. Move to a different plan when your needs change, for example upgrade when you bump into the limits of the free plan, or when you want features a higher plan includes. This is also where you handle payment details. Review what each plan includes before switching so you pick the one that fits.
Set the data keeping period. Choose how long leadmaps keeps your data before it is automatically removed. Set a longer period when you need more history to spot long term trends or to meet a record keeping requirement. Set a shorter period when you prefer to hold less data, for privacy reasons or to keep things lean. Older data past the period is cleaned up for you, so pick the window that balances your need for history against your wish to keep less.

Use cases

Add a colleague to help with reporting. Open Team members and invite the person by email, choosing the member role so they can work with the data but not touch billing or other people. Action: once they accept and sign in, point them to the Overview and funnels pages to get started, and keep their role as member unless they genuinely need to manage the workspace.
Rotate a key you think may have leaked. If an API key might have ended up somewhere it should not, do not wait. Open API keys, create a fresh key, update your site or tool to use the new one, then remove the old key. Action: removing the old key shuts the door immediately, and naming your keys clearly beforehand is what lets you swap the right one without breaking everything else.
Upgrade when you outgrow the free limits. When the Plan and billing section shows you are hitting the limits of the free plan, that is the signal you have grown past it. Action: review the higher plans, pick the one whose limits and features match where you are heading, and switch, so your tracking keeps running smoothly instead of bumping against a ceiling.

Tips

Give each person the smallest role that fits. Most teammates need member, not admin. Reserve admin for the few who manage billing, keys, and people, so an accident or a lost login cannot reach further than it should.
Name your API keys for where they are used. A key named “main-site” or “looker-export” tells you instantly what depends on it. An unnamed pile of keys means you cannot safely remove any of them, because you do not know what would break.
A key is a password, not a person’s login. Never put a key in a public place, never share it where it could leak, and replace it the moment you are unsure about it. People sign in with their own accounts. Keys are only for software.
Pick a data keeping period on purpose. The right window balances how much history you want against your wish to hold less data. Set it deliberately rather than leaving it unconsidered, especially if you have record keeping rules to follow.
Review who has access from time to time. People join and leave, and tools come and go. A quick look at your team members and your keys every so often catches the stale account or the forgotten key before it becomes a problem.