Feature Request - Clear User Attributes

replied on December 3, 2018

This is already available, unless I am misunderstanding the situation:

0 0

View 5 previous replies

replied on December 3, 2018

Hey Robert,

Yes this setting clears some of the attributes. But most of the time we have to clear all attributes to resolve an issue. This includes saved searches etc. It would be nice to mimic selecting all attributes in the admin console and removing. A bit like the above setting but a complete clear.

Cheers!

0 0

replied on December 3, 2018

My experience has been similar to Chris' experience. The "Restore" option in the client does revert settings back to default, but it does not seem to resolve certain issues that require clearing all attributes in the admin console.

As an example, in some instances user setting changes made in the client won't hold. A user will change scanner configuration, columns, etc., but they revert back to the previous state every time the user logs into the repository.

In those cases, the only way I've ever been able to fix the issue is to reset their attributes in the Admin console, which means we have to give more of our front-line IT support staff access to manage repository users.

On a side note, I've found that having users utilize the Sign Out or Sign Out of All Repositories option instead of just closing the client window seems to dramatically reduce how often we have these kinds of issues.

0 0

replied on December 3, 2018

It would be nice if the organization could specify a default attribute template that would get applied after the reset.

0 0

replied on December 3, 2018

You can actually! Sign in with a clean account, configure your settings, then go into the Admin console, export them, and import them into the Everyone user.

0 0

replied on December 3, 2018

Everyone to broad for what we need sometimes. Anyway, never mind for right now. I don't want to muddy the waters for this particular request. :)

0 0

replied on December 3, 2018

I agree. At one of the Empower conferences I spent some time talking to some of the devs/engineers about the idea of attribute settings for groups.

The biggest challenge they mentioned, which made sense, is determining how to handle inheritance/priority since multiple/nested group memberships can exist.

I'm sure they will find a way to make it work if demand is high enough, but the conversation did explain why it wasn't a "simple" change.

0 0

replied on December 3, 2018

Well, here comes some mud anyway.

In Active Directory, there are two types of groups. Distribution groups can only be used by email servers. Security groups are used for everything else, but can also be used for email distribution. I wonder if something similar could work here. It's still complicated, but it might help to have an entirely separate type of group. It comes with it's own set of complexities though.

0 0

replied on December 3, 2018

That was my thinking. Either separate "Attribute" groups, a section for setting "Priority" ordering for groups, or both.

For example, on the priority page, all groups would be listed top-down in order of priority/rank. The higher the group, the higher the priority.

If two or more groups apply to a user and have any settings that conflict, the value for the "topmost" group would take precedence.

If the list is global for all repository groups, then you have a clear hierarchy and no chance of two groups having the same priority level.

0 0

Question

Question

Feature Request - Clear User Attributes

Replies

Sign in to reply to this post.