Community shared activities & programs
J
Jonathan Eggerichs, PsyD
Similar to how the current platform doesn't make you reinvent the wheel by giving access to already existing activities or programs to use or adjust, would it be beneficial to have a place to offer and upload activities and programs that clinicians have created and are using with clients if they want to share?
Log In
K
Kietha Adams, MS, LMFT, ABC-Sexologist
I envision enabling professionals within the same company account to share resources across separate workspaces, improving collaboration, consistency, and efficiency. Quenza could let users send activities, programs, templates, and other resources directly to colleagues or contribute them to a centralized Shared Library. Authorized team members could browse, preview, and add resources to their workspaces. Permissions, contributor attribution, categories, search filters, and version updates would help organizations manage content while allowing professionals to customize it for their clients and workflows.
A typical flow could be simple: A professional selects a resource, chooses “Share with Team,” selects a colleague or group, and assigns view, copy, or edit permissions. The recipient receives a notification and accesses the resource in their workspace or the Shared Library. Team members could also browse the library for ideas, preview colleagues’ resources, and add customizable copies to their own workspaces. This process would fit naturally into daily workflows and encourage reuse.
Possible implementation steps could include creating a company-wide Shared Library module with clear access management. Resources can be flagged as private, shared with specific individuals, or made available to the whole organization. Permissions could be controlled at the resource and folder levels, with administrator oversight for organization-wide content. When a resource is updated, a simple versioning system could notify users of changes and allow them to accept updates or keep their customized copies. Contributor attribution could automatically track original authors and editors.
To support adoption, the rollout could include interactive walkthroughs, first-use tooltips, concise in-app guides, and brief introductions during onboarding or training. These measures would make sharing secure, transparent, flexible, and manageable for teams of any size.
Technical considerations include synchronizing permissions across workspaces, maintaining data consistency during simultaneous edits, and migrating existing resources when sharing is enabled. Authentication and user management must support detailed access controls, while real-time notifications and audit trails may require additional infrastructure. Product and engineering teams should collaborate on a secure, scalable solution.

Torben Tschechne
Merged in a post:
Share Activities?
w
wylie shipman
How about a "commiunity" category for pre-make activities? Users could choose to share activities for use within the user base, or choose not to. Obviously, every user would need to verify that the activity is clinically appropriate. If you did this, it would be helpful to have labels for modalities like ACT, CBT, DBT, etc. Thanks!
K
Kietha Adams, MS, LMFT, ABC-Sexologist
I envision enabling professionals within the same company account to share resources across separate workspaces, improving collaboration, consistency, and efficiency. Quenza could let users send activities, programs, templates, and other resources directly to colleagues or contribute them to a centralized Shared Library. Authorized team members could browse, preview, and add resources to their workspaces. Permissions, contributor attribution, categories, search filters, and version updates would help organizations manage content while allowing professionals to customize it for their clients and workflows.
A typical flow could be simple: A professional selects a resource, chooses “Share with Team,” selects a colleague or group, and assigns view, copy, or edit permissions. The recipient receives a notification and accesses the resource in their workspace or the Shared Library. Team members could also browse the library for ideas, preview colleagues’ resources, and add customizable copies to their own workspaces. This process would fit naturally into daily workflows and encourage reuse.
Possible implementation steps could include creating a company-wide Shared Library module with clear access management. Resources can be flagged as private, shared with specific individuals, or made available to the whole organization. Permissions could be controlled at the resource and folder levels, with administrator oversight for organization-wide content. When a resource is updated, a simple versioning system could notify users of changes and allow them to accept updates or keep their customized copies. Contributor attribution could automatically track original authors and editors.
To support adoption, the rollout could include interactive walkthroughs, first-use tooltips, concise in-app guides, and brief introductions during onboarding or training. These measures would make sharing secure, transparent, flexible, and manageable for teams of any size.
Technical considerations include synchronizing permissions across workspaces, maintaining data consistency during simultaneous edits, and migrating existing resources when sharing is enabled. Authentication and user management must support detailed access controls, while real-time notifications and audit trails may require additional infrastructure. Product and engineering teams should collaborate on a secure, scalable solution.
Ernst Jansen
Thanks for bringing this up, Jonathan! A community library where practitioners could share their own creations, from their own specialized field of work, sounds really valuable.
Curious how you'd envision the sharing working. Are you thinking more like a public library where anyone could browse and use what others have created, or something more curated?
K
Kietha Adams, MS, LMFT, ABC-Sexologist
Ernst Jansen
I envision enabling professionals within the same company account to share resources across separate workspaces, improving collaboration, consistency, and efficiency. Quenza could let users send activities, programs, templates, and other resources directly to colleagues or contribute them to a centralized Shared Library. Authorized team members could browse, preview, and add resources to their workspaces. Permissions, contributor attribution, categories, search filters, and version updates would help organizations manage content while allowing professionals to customize it for their clients and workflows.
A typical flow could be simple: A professional selects a resource, chooses “Share with Team,” selects a colleague or group, and assigns view, copy, or edit permissions. The recipient receives a notification and accesses the resource in their workspace or the Shared Library. Team members could also browse the library for ideas, preview colleagues’ resources, and add customizable copies to their own workspaces. This process would fit naturally into daily workflows and encourage reuse.
Possible implementation steps could include creating a company-wide Shared Library module with clear access management. Resources can be flagged as private, shared with specific individuals, or made available to the whole organization. Permissions could be controlled at the resource and folder levels, with administrator oversight for organization-wide content. When a resource is updated, a simple versioning system could notify users of changes and allow them to accept updates or keep their customized copies. Contributor attribution could automatically track original authors and editors.
To support adoption, the rollout could include interactive walkthroughs, first-use tooltips, concise in-app guides, and brief introductions during onboarding or training. These measures would make sharing secure, transparent, flexible, and manageable for teams of any size.
Technical considerations include synchronizing permissions across workspaces, maintaining data consistency during simultaneous edits, and migrating existing resources when sharing is enabled. Authentication and user management must support detailed access controls, while real-time notifications and audit trails may require additional infrastructure. Product and engineering teams should collaborate on a secure, scalable solution.