Another design edition: introducing teams on Albus
A new layer of privacy for your team within Albus
This Friday, I’d like to share the design thinking behind a feature that will change the way Albus behaves - teams.
At Albus, we're all about building a knowledge bot that facilitates open and transparent communication.
With the inception of teams, people managers will be able to assign employees and sources to specific teams.
When an employee asks a question, Albus can then respond to them based on which team they belong to and what sources the team has access to.
This lets people managers contribute knowledge collectively and makes it easier for Albus to retrieve information relevant to their teams.
This is what our design team likes to call role-based access.
For example, let’s say the Sales team and the rest of the company had different reimbursement policies mentioned in different documents.
As of today, since Albus doesn’t know which team a user belongs to, he will share the same information with both Sales folks and other people in the company.
With teams (that empower role-based access), privacy is maintained. This also allows people managers to restrict sensitive data to relevant stakeholders.
Our design team carefully architected the teams’ settings page in our dashboard such that CXOs, People Ops and people managers can define teams based on functions and information access.
By managing employees’ access to teams, they in turn also manage their access to the wiki Albus generates over time.
Does this sound interesting to you? Want to explore teams for your company? Set up a call with our team and an account manager will take care of your case personally.