AbriuPublic

For partners

How to work with Abriu: what each side does, how to request a new site's registration and what is restricted.

Abriu is designing its partner program with resellers, integrators, property managers, security companies and installers. This page says how it is already possible to work together today; the commercial terms are being defined with the interested companies, and nothing here promises a commission, price or territory. To talk, use abriu.app/partners.

What Abriu does and what the partner does

Abriu The partner
Registers the site, creates the panel and hands over the install code. Sells, supplies and installs the material (hub, terminals, locks, network).
Follows the hub from afar, around the clock, and updates the system. Does the physical installation and the handover to the manager.
Gives remote support to the site and the partner. Attends on site when something must be replaced or the network adjusted.
Maintains the panel, the app and the documentation. Knows the site and is its first contact, if so agreed.

Requesting a site's registration

Send Abriu, through the agreed channel, one business day ahead:

  • the site's name, as it should show on the panel and in the e-mails;
  • the wanted panel address: a short name, lowercase letters, digits and hyphens only, up to 32 characters (say, edificio-azul becomes https://edificio-azul.abriu.app). It cannot be changed later;
  • the time zone, if not Brasília's;
  • the first administrator's name and e-mail (the manager or the property manager), who gets the panel's invitation;
  • the site's contacts for Abriu (manager, caretaker, property manager: name, role, phone, e-mail);
  • how many doors and which terminals, and whether there is a vehicle gate;
  • whether the hub will use Wi-Fi (the network's name; the password is typed by whoever downloads the file, and never stays with Abriu).

Abriu returns the panel's address and the first-boot file or the code, valid for 14 days.

During the installation

Abriu's support is available at the agreed hours on the installation day: confirming the hub reported, resending an invitation, making another code. What the partner sees and what Abriu sees:

The partner sees Abriu sees
The panel, if the manager created a user for them. The fleet: whether the hub is up, the version, the terminals online, the disk, the power, the backups. Never people's data.
The public status page. The public status page.
The terminals, physically and on their screens. The hub from afar (remote screen and shell), with each access recorded.

After the installation

  • Abriu is told on its own when something fails (hub without news, terminal offline, disk, power) and handles what it can from afar. When someone is needed on site, it calls the partner, if so agreed with the site.
  • The client opens tickets through the panel; Abriu answers by e-mail and, when it is the partner's case, forwards it.
  • Replacing a terminal, hub or lock: the partner does it, with Abriu reinstalling the hub from afar when needed (see Replacing or reinstalling a hub).

With the partner's brand

A partner can offer the system to its clients under its own name. Abriu registers the partner's brand and chooses it on each of the partner's sites; a site without a brand keeps Abriu's. Send Abriu:

  • the name, as the clients should read it (for example, "Bem-vindo(a) ao …", "Welcome to …");
  • the logo: PNG, SVG or WebP, up to 512 KB, preferably horizontal, with the name and a transparent background, and, if there is one, a version for dark backgrounds;
  • the icon: a square PNG of at least 192 px (512x512 recommended), up to 512 KB, readable at the size of a browser tab.

With the brand, the clients see the partner's name, logo and icon on the panel (titles, sign-in, menu, the browser tab icon and the app installed on the phone), in the e-mails, in the PDFs, on the status page and in this guide opened with ?site=<id>. The addresses stay Abriu's (<id>.abriu.app, status.abriu.app/<id>), the e-mails go out from Abriu's address (the panel's under the site's name, the central's under the partner's), and support stays with Abriu, which answers under the partner's name.

What is public and what is restricted

  • This guide is public: it can be sent to any installer.
  • The panel belongs to the site: the manager decides who has a user, with which profile, and can deactivate the partner's whenever they want.
  • The fleet (fleet.abriu.app) belongs to Abriu's team and requires a login: it holds the contract data, the contacts and the follow-up of every site. A partner does not need it: what they need to know is on the site's panel, on the status page and in this guide.
  • Remote access to the hub (screen, shell) is Abriu's alone, recorded at each use.

Material for the partner to present Abriu

  • The site, abriu.app, with what the product does and the plans.
  • A site's status page, as an example of transparency with the residents.
  • This guide, so the customer sees what the installation involves.