Do I have to put my building on the public map?

No. Most private buildings do not. A join code is how residents reach chargers that no passing driver can see.

Where do I get our building’s code?

Codes are issued per location. If you are a building admin, the account holder above you has it. If you are the account holder, it is on the location.

Does a resident need a new code if we add a charger?

No. The code attaches the person to the location. Chargers added there afterwards appear for them without anyone doing anything.

Can I stop someone using our chargers?

A resident can be removed from the building. A per-driver block list exists only at a home charger, where the host runs it from the driver app and a blocked driver sees the charger as closed rather than as blocked. The console has no block list for the chargers you run there.

What is the difference between a building code and a fleet code?

A building code gives a person access to a place. A fleet code makes a person’s work charging bill the company. They are separate mechanisms and a driver can be on both.

Run the site

Join
codes.

How residents get onto a building’s chargers, and how drivers get onto a fleet, without either of them appearing on a public map. One code, entered once.

What a code is for

Plenty of sites should not be on a public map. A residents’ parkade does not want passing traffic. A depot does not want the public. But the people who belong there still need to find the chargers and use them.

A join code is how. The person enters it once in the app and from then on the site is simply there for them. No map listing, no public discovery, no gate for anyone else.

Building codes

Building codes are issued per location. That matters if you run a portfolio: each building has its own, so giving a resident the code for one building does not hand them the rest.

Get residents charging

Do it yourself

Get the join code for the location.
Send it to residents with a link to the app. A move-in pack, a notice board and a resident newsletter all work, and the notice board is the one that actually gets read.
The resident installs the app, enters the code once, and the building’s chargers appear for them.

Or just ask EVII™

How many residents have joined the building?

Who charged here last week?

Put the app install instructions next to the code. A code with no app is a support call.

The Building Join Code card under Location Settings for Sample Towers (sample data), seen by a test Operator. It explains that this per-location code is for residents of the building and that anyone with the link can register or switch their account into the location. Active code is the sample code SMPL01, with its generated date and a Copy join URL button. The join link reads https://app.example.test/join?code=SMPL01, and the footer says 14 users joined via this code. — The Building Join Code card, under the location’s Location Settings: the active code, Copy join URL and the join link. Sample screen with test data.

Join a building or fleet dialog in the driver app, opened from the Account sheet. Under an illustration of city buildings, the text reads Enter the 6-character building code or the 8-character fleet code you were given. The sample building code SMPL01 is typed into the code field, above Cancel and Look up buttons. — In the driver app, Menu, Account, Join a building or fleet: the resident types the building code and taps Look up. Sample screen with test data.

Once joined, a resident sees the building’s chargers, charges at whatever price you have set, and appears in your reports like anyone else. Chargers you add to that location later show up for them automatically.

Fleet codes

A fleet has two ways in, and the second one is the one to use if you have more than a handful of drivers.

An invite code. You give it to a driver, they enter it once in the app, they are on the fleet. Right for contractors, for anyone on a personal email address, and for one-off additions.
Join a fleet in the driver app, with the invite code typed in. Sample screen with test data.
Email domain auto-attribution. Register your company’s email domain and anyone who signs up with an address at it is attached to the fleet automatically. Nothing to distribute and nothing to maintain when you hire someone.

For a long list, do both

Bulk upload the spreadsheet from the fleet Drivers tab, one email per row, and register the domain as well so new hires attach themselves later without anyone doing anything. The domain alone is not enough on Google Workspace: auto-attribution runs on password signup and is skipped on Google sign-up.

Joining a fleet is not the same as joining a building. A fleet code decides who pays for a driver’s work charging. A building code decides where a person can charge. A driver can easily need both: the fleet code so work charging bills the company, the building code so they can use the chargers in their own garage. See Fleet Admin for fleet mode and personal mode, which is the part drivers actually have to understand.

Leaving

A resident can remove themselves from a building in their own app.
A fleet driver is removed by the fleet admin on the Drivers tab. Future fleet-mode sessions stop immediately. It does not reverse sessions already run, and it should not, because that energy was genuinely delivered. Kill their keyfob at the same time.
Anyone can be blocked at a home charger by its host, in the driver app. A block beats everything, including the free list, and the blocked driver sees the charger as closed rather than as blocked. The console has no block list for the chargers you run there.

What a code is not

Not a password. Treat it as semi-public. It is how residents get in, so it will end up on a notice board, and that is fine.
Not a payment method. A building code gets someone access. They still pay whatever you charge.
Not a block list. A code lets people in. It is not the way to keep one person out, and changing it changes it for everyone.