'View & Share' permission in notes
Users who only have 'view' access to notes cannot share the document. Please add a sharing feature without editing privileges
Functional hyperlinks on uploaded documents
Hello, I've noticed hyperlinks on uploaded documents like pdf and power point don't work. Is there any way to make these links accessible? Thanks.
Export Pending Invites
It would be good to be able to export those that have been invited but are still pending on a group so that they can be contacted.
Additional dropdown option for Notes and Templates.
Is it possible to have an additional dropdown option for the notes tab? I would like to have a way to separate or filter my notes into two separate categories without utilizing the template option. Would this be possible or would there be an easier way to make this work? Thank you!
Integrately an easy and cheap Zapier alternative
Please integrate with 'Integrately'. An easy to use and cheap Zapier alternative.
When you invite people to a new group, you select invite from - people list, can we exclude those that have already been invited. Also can we add more than 100, or at least have a way to select those not already invited.
It would be nice if the padlock could be a different colour when it has restricted permissions so you can quickly see in list view those documents that are shared with All Members rather than restricted.
Add tasks/notes via email
It would be great if clients could add both tasks and notes via email versus having to be logged into the portal. The portal for many is just one more place they need to go to 'work', which can be a deterrent for many. If they had a custom email address, like Asana or other PM tools, they could simply add the task via email and see updates.
Enable 'Deny' Permissions in addition to 'Allow'
Sometimes it's easier to mark certain notes and folders as unavailable to specific members, rather than make them 'available' to everyone else. This would be especially useful in nested folders where when a folder is created, permissions are inherited. In the current scheme, if I have restricted folders inside a public folder I have to allow all members to acces the parent, and allow only specific ones to the private ones. However, if I create a new restricted folder it creates it with the default parent permissions (public) insted of defaulting to private, which could create confidentiality problems if contributors are not careful. Our current workaround is to only have private folders as root folders to ensure no one makes a mistake.