The tools your project runs on, connected.
AUVY syncs your project's mail, calendars, chats and files from Outlook, Teams and SharePoint, read-only and signed in as each person. Every command a connection may run is published word for word on its page.
All connections
One row per system.
Each row opens what the system reads, what AUVY may prepare in it and every command it can run.
Full sync
The history first, then every new item.
The first sync copies the mail, meetings, messages and files you choose, back to a start date you pick, and after that AUVY keeps up with every new item. Sync only reads, through each person's own sign-in, and it is part of every licence.
Rules
Every call passes the same checks.
Before AUVY installs a connection, it is written down in three plain files: the commands it offers, whether each one reads or changes something, and one page of instructions that your team and AUVY both follow. Every call then passes these checks in order, whoever makes it, and if one fails, nothing happens.
- Who is askingA named person, or AUVY acting for one.
- AllowedThat person has been given this command.
- ConfirmedAnything that changes or sends something waits for a person to accept it.
- Signed in as youWith your own login. The keys stay in AUVY's keyring, never in the connection.
- Fenced inThe command runs in a sealed space and reaches only the addresses its rules list.
- Written downEvery call is logged with who, what and when.
The files follow HCP, an open format AUVY started for describing what a tool connection can do. About HCP →