Learn how teams use Spaces, a shared Knowledge Base, roles and permissions in disQo.ai
Collaboration in disQo.ai helps teams work from the same trusted knowledge while keeping individual work organised and private.
Teams can create Spaces within their organisation for specific projects, clients or areas of work. Each Space has its own members, shared Knowledge Base, connected apps and analytics.
Spaces
Learn how Spaces separate work by team, project or client.
Shared Knowledge Base
See how Space members can reuse shared project knowledge.
Roles and Permissions
Understand Organisation Owner, Space Owner and Space Member access.
We are rolling this feature out gradually to ensure the best experience.If you would like to enable Collaboration for your organisation or learn more, please contact our sales team at enquiries@tiqtoq.co.uk.
You can switch between your personal workspace and any Spaces you belong to using the workspace switcher.When you move into a Space, disQo.ai updates the available Knowledge Base, connected apps and navigation.This helps keep work for different teams or projects separated while still allowing shared resources to be managed centrally.
Access to Spaces is controlled through roles.Organisation Owners can manage organisation-level settings and control access to Spaces.Space Owners can manage their Space, including its members and settings.Space Members can work within the Space and use its shared resources according to the permissions available to them.
Space Owners can manage who has access to their Space.Organisation members can be added to or removed from Spaces, and new organisation members can be assigned to the appropriate Spaces when they are invited.This allows organisations to give people access only to the project knowledge and resources relevant to their work.
Space-level analytics provide visibility into how disQo.ai is being used across the team.Depending on the features available to your organisation, this can include activity, agent usage, storage and ROI information attributed to the relevant Space.This makes it easier to understand adoption and usage at a project or team level rather than only across the organisation as a whole.
A project team creates a Space and uploads its agreed requirements, test strategy and testing standards to the shared Knowledge Base.Each team member continues working in their own private chats and workflows, while using the same trusted project information as context.When someone creates a useful output that should be reused by the wider team, they can save it to the Space Knowledge Base for other members to access.