# Managing business applications from one dashboard > When email, files, a website assistant and access control sit in separate software, each keeps its own user list and permissions. Source page: https://dblinx.net/en/rehberler/is-uygulamalarini-tek-panelden-yonetmek --- Administration # 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. 3 min readPublished: 17.10.2026 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. **Tip**When planning a transition, start by cleaning up your person and department list. A single dashboard delivers the most benefit when it starts from a clean list. ## 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. [Ecosystem](https://dblinx.net/en/ekosistem)[Document: granting product access](https://dblinx.net/en/belgeler/baslarken/urun-erisimi-verme)[Document: removing a person from the organization](https://dblinx.net/en/belgeler/baslarken/kisiyi-kurumdan-cikarma) ## Frequently asked questions Can I get the applications one at a time? Yes. You start with one product, and the others are added to the same dashboard later. Does a single dashboard create a security risk? Even though management sits in one place, data is kept in a separate database for each product, and every action is tied to a permission. How is access updated when an employee changes department? In SmartFiles, department-tied area permissions change to match the new department. In SmartMail, access to the old department's mailboxes is removed, and the person is added separately to the new department's mailboxes. ## All products in one dashboard Add a person once and grant access to every product from there; when an employee leaves, shut off their access in a single action. [Request a quote](https://dblinx.net/en/teklif-iste)[Get in touch](https://dblinx.net/en/iletisim) ## Other guides - [AdministrationHow to revoke email access for a departing employee? A step-by-step access revocation guideA departing employee's email access should be revoked on their last day, their sessions ended, and their correspondence handed over to a colleague. Shared mailbox and file permissions are also revoked the same day. Being able to revoke access from a single list across all services removes the risk of a forgotten account.6 min read](https://dblinx.net/en/rehberler/calisan-ayrilinca-erisim-kapatma) - [AdministrationWhat is the principle of least privilege? Applying it to email and file access in organizationsThe principle of least privilege means giving each person and each system only the narrowest access needed to do their job, and no more. If an account is compromised or a mistake is made, the damage stays limited to what that account can reach. The principle is applied by granting permission based on job, role and department, and reviewing it regularly.6 min read](https://dblinx.net/en/rehberler/en-az-yetki-ilkesi) - [SecurityWhat is CEO fraud? A guide to protecting against fake IBAN emailsCEO fraud is an email scam in which an attacker posing as an executive or supplier convinces an employee to make an urgent payment or pay a fake IBAN. The attacker wants the payment redirected to another account. These emails often carry no malicious link or attachment, so they easily pass through standard spam filters.6 min read](https://dblinx.net/en/rehberler/ceo-dolandiriciligi-sahte-iban)