CiviCRM Community Forums (archive)

Hi,
I want to give to my users the permission to create and administer tag (not tag set or reserved tag)?
It's possible or Not?
Thanks in advance

Hi,

Sorry to come back to an old thread: I gave team users this permission, but they still get "Access denied.You are not authorized to access this page." when trying to administer or create new tags

I modified the navigation menu so it wasn't only restricted to civicrm administrators, the navigation menu is correct but the permission isn't.

I tested in two different civicrm install. does it work on your side?

X+

I see this bug too. Users need "Administer CiviCRM" permissions to use /civicrm/admin/tag?reset=1

Administer tagsets is not enough.

Hi,

Have this bug been reported or solved in new versions? It's still present at 4.4.6

I have a half-baked patch that fixes this problem (by changing url from civicrm/admin/tag/* to civicrm/tag/*, working in production in 4.2 but should be easy to to port it to 4.5). Set up an issue (https://issues.civicrm.org/jira/browse/CRM-15371) and should submit first take on the patch soon.

m

pretty much every url (or most urls) under civicrm/admin require 'administer civicrm' permission

if u'd like to take a look at and help improve the permissioning system for 4.6 that would be great

lobo

Hi Lobo,

I'm not a coder, but what about create a new path /management and put part of actual /admin menu entries there? Then, admin permission should only apply to REAL  admin (sensitive) tasks, and other tasks, are easier managed with ACL/menu tools.

If that has sense I could open a ticket...

Regards,

Joan

restructuring the menu system will be a fair bit of work. If your org or client can sponsor a developer to do the needful, that would be great. Their first task would be to come up with a more detailed plan and do a mapping of current urls to proposed new urls

lobo

I'm sorry but my client has not resources to sponsor it.

But I could work on it as far as my skills go :-)

Then, if you think my focus in this issue is interesting (the right way), I could first analyze all the actual /admin menus and list all I think go out of and, instead, go under the new "management" menu. After it, we could discus it.

Second, could we use alias to point new management/ menus? If it is possible, we could implement this feature without rewrite lots of links. If not we must, first, detect and correct ALL menu links which are going to change. I can work on it if needed.

Ps.: we could work, at first, in admin/tag > management/tag migration, but it's maybe more interesting work on all menus we think are suitable to migrate from admin/ to management/

Ps.: I'm not really experience in software development... I beg your pardon if my focus is not the best one :-) But I'd like to help to improve, modestly, this wonderful piece of soft.