The ability to limit posting by contents of session using advance security settings.

33 votes

International, and perhaps large domestic organizations, need the ability to limit who can post sessions by the account codes in the session. If I am limited to using the Togo account codes, I should not be able to post sessions created by the Tanzania office.

Customer Suggestion Suggested by: Laura Reifschlager (15 Jul) • Upvoted: 03 Sep • Comments: 2

Comments: 2 Oldest | Newest | Most likes | Fewest likes

16 Jul
Dav Hayner
I am not sure it is only large organizations. I think that this would be used by organizations domestically if they wanted to control their departments, for example, and limit posting to that department's chief.
05 Sep
Steven Seamans
This would be hard to implement, I think. The users are given their rights to the database. The database does not view a session as "it belongs to the person/group etc" so to try and force the system to view that would be very difficult. Here at K-State we have 5 Databases that we use in my office. Each one has its own dedicated departments, so for your example, you would be in one database, and the Tanzania office would be in another. You guys would have your own rights to your own database and never see each other's sessions etc.