Managing multiple business applications from a single dashboard: people, departments and access in one place
When email, files, a website assistant and access control run on separate software, each keeps its own user list, its own permissions and its own invoice. A single dashboard lets you define a person once and grant access to every application from there.
Organizations usually buy software one piece at a time, as the need arises: email first, then file sharing, then a chat tool for the website. Before long, each one has its own user list, its own permission screen and its own invoice.
The hidden cost of managing things separately
- A new employee gets set up separately in each system; one gets forgotten.
- A department change has to be updated by hand in every system.
- A departing employee's access stays open in one system.
- There's no single answer to who has access to what.
- Usage and invoices are tracked on separate screens.
How does management work in a single dashboard?
- A person is added once. The employee is invited and sets their own password.
- A department is defined once. File-area and shared-mailbox permissions across applications are granted through the department.
- Product access is granted from one place. Which application a person can use opens up on a single screen.
- A departing person is removed in one action. Their access closes across every application at once.
A single dashboard doesn't mean a single database
Even though management sits in one place, each application's data should stay separate. In a sound structure, each organization's data is kept in its own separate database for each application; a problem in one application doesn't reach into another's data.
How does DBLinx do this?
- Organization dashboard: People, departments, product access, domain, usage and purchases, all in a single dashboard.
- Department once: In SmartFiles, access to areas is tied to the department and changes when the department changes. SmartMail mailboxes are assigned to a department; a person's mailbox access ends when they leave that department.
- Removal in a single action: A person removed from the organization loses access across every Smart product at the same time.
- Separate database: Each organization's data is kept in its own separate database for each product.
EcosystemDocument: granting product accessDocument: removing a person from the organization