Administration

Organisation admins run their organisation from the Admin console (avatar → Admin console). Pick the organisation at the top; every page acts on that organisation. Back to app returns to your workspace.

Organisations

Organisations lists the organisations you administer. Open one to see its tabs:

• Overview: the organisation's details, and the Statistics time zone used by dashboards and reports;
• Members, Devices, Sites (below);
• Apps: the applications enabled for the organisation. Applications are enabled by ANSCENTER; you need at least one before you can add members.

To set up a new organisation, contact ANSCENTER.

Members

Organisations → the organisation → Members.

1. Click Add member.
2. Enter the Email, choose the application and the App role (for example teacher or security).
3. Tick the extra roles only if needed:
   • Organisation admin: may open the Admin console for this organisation;
   • Org builder: may change the data model and rules (always an organisation admin too);
   • Org developer: may write scripts (available on request).
4. Save. The person signs in with that email.

For many people, use Import CSV: Download template, fill it in (UTF-8, the exact header row), upload it, check the dry run, then Import now. Existing members are updated; nobody is deleted. Export CSV downloads the current list.

The email and application of a membership cannot be changed: remove the member and add them again.

Devices

Organisations → the organisation → Devices lists the boxes of the organisation.

• Import from QR: add a box by scanning, uploading or pasting the device QR code from ANSMIND.
• Name this device: a label your team recognises. It changes nothing on the box.
• Remove device from organisation: the box stops belonging to the organisation.

Only boxes listed here send registered events, with their site. See Connect your boxes.

Sites

Organisations → the organisation → Sites.

• Add site / Edit site: the Site name and an optional address.
• Assign each device to its site, so its events carry that site.
• Limit a member to one site, or leave them on All sites. A member limited to a site sees only that site's events and numbers.
• Add an existing member moves a member of the organisation into the site; no new account is created.

Branding and custom domain

Branding makes the CMS look like your organisation's own product. Changes apply to everyone in the organisation.

1. Set the Name (first line of the header) and the Subtitle (second line).
2. Choose the Primary colour. Buttons, links, the active menu item, charts and the sidebar all follow it.
3. Choose the Sidebar style: Solid or Light.
4. Upload the Logo, the Logo on dark, the Favicon and an optional Login background.
5. Choose the Default language visitors of your domain see first. Each user can still switch under avatar → Language.
6. Check the Preview, then click Save branding.

Custom domain: ask ANSCENTER to assign a domain such as cms.your-ward.gov.vn. Then create the DNS CNAME record shown on the page. Visitors on that domain see your branding before they sign in.

Default for members

Default for members decides what members open when they sign in, if they have not chosen their own workspace.

1. Choose the Application (or No default).
2. Choose the Site or All sites.
3. Choose the Start page: The application's home, or a page from the menu. Edit menu → opens the menu editor.
4. Click Save.

A member who ticked Open this workspace every time I sign in keeps their own choice.

Security (MFA)

Security (MFA policy) → Two-factor enforcement lets you require two-factor sign-in per role.

1. Find the role.
2. Switch it to 2FA required at login. It takes effect at that person's next sign-in.

Each person sets up their own two-factor authentication under avatar → My settings → Two-factor authentication → Enable 2FA, with an authenticator app.

tip

Require 2FA at least for organisation admins.

If the page says "The sign-in security policy is managed by ANSCENTER", ask ANSCENTER to change it.

Support access

Support access decides when ANSCENTER support may look into your organisation's data and rules, and shows what they did.

• Policy:
  • Always (ANS support may look in): support can open your organisation at any time; every visit is listed.
  • On request (only inside a grant): support can open it only while a grant you gave is active.
  • Never (only what we share): support works only from what you send them.
• Grant access…: choose a Duration and a Reason (for example "check why the late rule did not run on Monday"), then confirm. You can Revoke a grant at any time.

info

This feature may not be enabled for your organisation yet — contact ANSCENTER.

Long-term archive

Events are kept for your organisation's retention period, then deleted. The Long-term archive keeps older months as archive files instead, so you can still search them, for example for a plate.

• Keep history beyond retention: switch it on, choose Keep archives for (years) and write why you keep the data.
• Archived months: the months kept, with Kept until and the files to download.
• Search the archive: find a plate (or any subject) across up to 36 archived months. Results appear under Searches and exports.

Pictures are not archived: they are deleted with retention.

warning

Plate history is personal data. Keep it only as long as you need it, and record the reason.

info

The long-term archive is available on request. If the page says "The long-term archive is not switched on", nothing is archived and expired months are deleted as usual.

Where your data lives

The Admin console Overview shows Where your data lives: the database that holds your organisation's events and data. By default this is the ANSCMS Shared database in Google Cloud, Singapore region.

Dedicated databases, External databases (your own) and an on-site Data Node are available on request. While data is being moved, pages are read-only until the move finishes.

info

This feature may not be enabled for your organisation yet — contact ANSCENTER.