Feature Request
Hoping to bring this back to attention. This is one of the few hard limitations that is keeping me from using noloco with additional user groups. For now we have many employees with different permissions using our app and its very possible and easy to tag someone in an area that they cannot access. I want to bring our clients into the app but at present they would be allowed to tag any of my team, most of whom never have direct contact with the client. It’s a recipe for confusion all around so my company continues to use other services such as Basecamp for our clients.
Hey @onlymatt, you can limit mentions to users in the same role/group in the Noloco user table by creating a permission for that role/group so they can only see each other. You would have to create a permission for each user group though. It’s not exactly what you and @buildwithjoel are requesting but you can use this workaround in the meantime. Hope this helps to encourage you to use the comments/mentions feature within your company.
It would be great to hear your ideal solution @onlymatt
As we mention above, we do give you control over who can get tagged, but adding the different dimension of context would make that configuration much more complicated, so it would be great to hear what you would need
@carlos solution does actually solve the large issue of being able to involve my clients in our app so that’s much appreciated. I can keep the client permission from tagging the field employee or warehouse permission so that’ great.
Other than that it comes down to how our information is partitioned among my team. I have many contexts where for example field employees and directors need to be able to tag eachother and just as many where they don’t because field employees don’t have access to the page. Setting the permissions at the user level is ineffective here. But, since they are all my employees or team members I don’t consider it a large issue, more of an aesthetic or incidental issue if a director were to unwittingly tag a field employee on a page that they can’t access.
That’s great @onlymatt - happy to hear we have a solution for you.
We’re definitely interested in coming up with something more versatile for comment mentions specifically
It could be different filters for comments on different tables, but it gets complicated to setup and maintain
@darragh given that there is the work around provided I would say my needs are largely met. The ideal solution would be tagging is only available to those who can view the page automatically. If that weren’t possible to do then I’d favor the current set up over having to manually set comment tagging permissions throughout. Basecamp is essentially set up that way now, where you have to manually select which users will be on a project when it is setup and its not an ideal level of maintenance for my team.
Just wanted to contribute how I see this in practical terms (the context aspect of tagging conditions). If they functioned like visibility conditions, it would be absolutely magical.
For example… can tag users whose user record…
(pick your user record field)
(pick the current page’s record or something from > logged in user)
(pick your field)
Then you can only tag people matching that condition.
TLDR: Can restrict tagging to users that match a condition related to the current page’s record, or the logged in user’s record.
This might actually be a very interesting solution, thanks for the suggestion @buildwithjoel
