I've actually never heard of that extension (and Google didn't reveal anything), so you'd have to check with whoever wrote it. It might take some effort for them to update it. If it's open source, you could look into contributing a solution yourself.
That said, allow me to plug two solutions of my own, as alternatives to the user creation wizard:
The Add ...
There's no other way out-of-the-box, but you could create your own solution (e.g. a Custom Page) which exposes this functionality to the right people. Behind the scenes it then needs to impersonate an administrator user to do the actions.
It is currently not possible to separate this from the System Administrator role. We introduced "System Privileges" in our 8.2 cloud release, and SDL Web 8.5 (due later this year) will include this.
Check the following links for more information:
List of privileges
SDL Web Privileges
No. Although for full access to manage users and groups you need to be a system administrator, it is also possible to grant the Permission Management right to a user and thereby enable them to manage rights and permissions within a given publication (and IIRC some limited access to the User/Groups management screens).
You will need to decide for yourself ...
Two things spring to mind (I'm sure there are more!):
You need to be careful that by disabling users that you do not 'block' items that are going through Workflow. This may be a problem if, for example, you disable all of the users in a particular group that are needed to approve content.
You may also need to keep in mind that although you have disabled a ...
You can user following for get the username & Description
var settings = Tridion.UI.UserSettings.getJsonUserSettings(true)
var userName = settings.User.Data.Name;
var description = settings.User.Data.Description
All of these actions will trigger events in the backend. It would be relatively simple to write an event that captures it and writes it somewhere like a database.
Here's a good starting point: https://github.com/NunoLinhares/tridion-2011-reporting/tree/master/Tridion.Extensions.Reporting
The Group scope (defined on the General tab in the CME) determines in which Publications the Group is available/visible.
The membership scope (defined per Group membership in the Member Of tab in the CME) only defines the scope of a particular Group membership.
Groups are often used as Roles (e.g. Author, Editor, etc.) in which case the Group scope is ...
I noticed the current behavior and was surprised enough to post about it. But I didn't realize any changes and just assumed I was mistaken before that you could add members from within a group.
I'm actually seeing the same behavior from 2013 SP1 and 2011 SP1, so any changes aren't specific to 2013. Are your differences for 2011 GA and earlier?
So for 2011 ...
Depending on the locks being accidental or intentional you might try programmatically unlocking on a fixed schedule (like 04:00). If people lock items for a purposes you would not want them unlocked (even by an admin). Note that "unlocking" comes in two flavors: checkin or cancel checkout. Accidental locks should normally be cancelled but incidental ones ...
I have implemented the same type of feature in my project.
Here are the steps that I have followed -
First read the all the tasks from that workflow process.
Then read the group involved in that tasks.
After that from Group read the list of users.
Hope this will help you.
For us, the user was specifically granted access to Folders/Structure Groups and had Workflow tasks assigned to him. Once the access was removed and Workflows finished, the user could be deleted.
SELECT * FROM [Tridion_cm].[dbo].[TRUSTEE_ORG_ITEM_PERMISSIONS] where TRUSTEE_ID = '164'
SELECT * FROM [Tridion_cm].[dbo].[WFL_ACTIVITY_INSTANCES] where ...
I can't think of many things that would have a user "in use". Perhaps you could check if it is an assignee in a workflow.
Beyond that, it might be possible to find out using a database query. (Of course, any queries that might modify the database should always go via the API, to stay in support, but a SELECT is fine.)
For this kind of thing, your best bet ...
AFAIK, it is not possible to manage user management without system administrator access OOTB.
The main thing to note, in Tridion UI, user management is part of administration tab which is available to you only if you are administrator.
There is a work around that can be implemented:
Create a custom application and implement functionality required like add ...
The one obvious way would be to remove the publishing permission however doing that will also remove the permission to publish.
As per your description, it seems, you just want to remove permission to remove from publishing queue however not block the publishing for the users of that group.
In such a scenario, you can develop a GUI extension which will ...
The Tridion Sites OOTB Installed system UI to Search and add users will not work for SAML enabled system, because of DOMAIN ! = LDAP
if you use Domain users then they are windows users, and you might need to configure the services to use windows auth.
In order to search and add LDAP users for Content Porter, Templating, and core services.
The alternative way ...
Yes. Users must be a System Administrator in order to fully manage another user's accounts, memberships etc.
As Dominic points out in his answer, you can grant users some ability to manage permissions and rights within a publication and some limited access to the account management screens.
You could, of course, create an alternative interface to update ...
No, the Content Manager does not track those kinds of changes. You will need to create some kind of extension to do this yourself. I'd suggest using an Event Handler.
Be aware that tracking changes to just users would not necessarily be enough to achieve your requirement. Users are typically added as members of Groups and those Groups are then given certain ...
It's not the answer you want but the only out of the box way for this is to select (All) users and then use the User column to sort/filter according to your needs. This is more of an issue if you've 100's of users publishing (as opposed to just in the list)... in which case you're looking at a GUI extension (that I'd certainly love to install and feedback ...
Let me add background on how I typically design authorization setups.
"Does this means the Group: 010_Global_Building_Blocks-Editor will
show up only in these 2 publications under their Security Settings as
No, this means users that belong to this group will only see those two Publications. As Pankaj mentions it is related to the ...
The General tab shows the membership scope of your group - 010_Global_Building_Blocks-Editor and this will come as ALL Publications
The Member of tab will shows all groups of which this group is a member and their specific membership scope (2 Publications for Editor Group). The Membership scope will be the Union of these groups - 010_Global_Building_Blocks-...
I appreciate everyone's input on this error. The only setting that needed to be changed was the User Right Assignment setting by adding Authenticated Users. I have updated the test GPO to only include this setting and it appears to be working as expected.
You're almost there. The reason why they can execute any action is because they are setup as Workflow Administrators. They should not be workflow administrators since this role allows you to - for instance - take over workflow tasks from others.