Create a single Knowledge Base that can be accessed by multiple people for company use.
j
jamesprimiani
Have Recall be accessible by multiple different people all accessing a single Recall database. This would allow a company to disseminate information to employees and keep a tight watch on what information is being shared so everyone sees the same thing.
Log In
Sankari Nair
Hey James, thank you so much for taking the time to share this feature request. I'm curious: do you think it resonates with this feature of shared spaces? The idea is that each person has an individual knowledge base, and there'd be shared spaces that you can have other people access and contribute to. https://feedback.recall.it/feature-requests/p/shared-workspaces-for-recall
j
jamesprimiani
Sankari Nair As a company, Shared Spaces isn't really what we would need Recall for. In our Recall, we house several different types of information, for instance, our Employee Handbook, and employees can ask recall questions about the policies in the handbook. We also would love to be able to house firm notes about all the other companies we work with, and have Recall be the central point that employees can ask questions on those companies, but not have to worry about the content of the information, just be able to ask questions. This would give us the ability to control the information and add to a single point of contact, instead of having to worry that all the other employees add the information to their own knowledge bases. It's a fantastic tool for housing a "company library". Superior to SharePoint or just storing files on a drive. Having the ability for several users to log into a single knowledge base would be game changing for us. I'm sure for several other companies too, if they're smart!
A space where an admin can allow access to users that cannot delete the items in the KB, just use them, is what would be awesome.
S
Sankari Nair
jamesprimiani hi James,
I actually do think the shared space could work. Imagine within Recall, there was a space where you stored the Employee Handbook, written notes, and all of your company knowledge, and everyone else could have access to it. They could chat with it, and those with the right permission could even add to it. Am I missing something in terms of what the gap would be?
j
jamesprimiani
Sankari Nair I went back and re-read the Shared Spaces proposal. I'm imagining that could work. It depends on the implementation of it. There needs to be guardrails that allows the admin to assign access with specific permission sets (Cannot delete, contributor, etc.). You asked a few questions regarding Shared Spaces. I'd love to put in my two cents:
How would you want to switch between workspaces?
For the ADMIN running the instance that others share, I'm thinking an Outlook-like interface, where you have two distinct email addresses easily accessible from the same screen. And be able to drag and drop info from the admin side to the user side.
What permissions would be most important to you?
Read Only, Contributor, Admin, Editor(can edit content)
How do you envision discovering and joining shared workspaces?
Users should simply get a link, sent by an admin, and the users experience can simply be the existing Recall screen as it is today.
What other collaboration features would enhance this?
Recall is an awesome platform for knowledge sharing. For our purpose, maybe having a space for comments- when users have ideas for content change or addition, so an admin can take action on that.
Question: Is there a timeline for roll out of Shared Spaces? And if you do move ahead with it, it would need to be "Retro". Meaning would I be able to add a shared space to my existing Recall?
Oh, and any thoughts on letting companies be able to brand the app with the company name? (Keeps competitors from knowing what we use)
Thank You Very Much for your time!