45 results found
-
1 vote
-
24 votes
-
1 vote
-
Pass traits through the SSO token
For cases where passing user and account traits via the JS SDK isn’t possible, it would be great to be able to pass traits via an SSO token.
4 votes -
Be able to export SSO logs
Developers need a way to be able to review logs, compare failures to their own system, so being able to export the logs (or adding an API endpoint) would help them get that data out of ZenRep for troubleshooting.
2 votes -
User has more than one email address, but there's no way to connect them to the same profile
User has more than one email address, but in ZenRep, you can only have 1 email per user.
So if the user uses a different email address, it doesn't pull in their tickets, ideas, votes they created with their other email.
This makes it hard for agents to get a clear view of the user, their history etc...
2 votes -
Admin to set user traits
Allow admins to set user traits (Account type, value, etc.) rather than just allowing these to be set using the API.
11 votes -
In-app SSL key uploads
Let admins upload their own SSL keys instead of having to contact customer support to manually do it.
1 vote -
grant a single user access to multiple forums by email address
Right now, the only way to grant a user access to multiple forums at once is with SSO. It would make things quicker to be able to do this with users you grant access to via email invitations.
0 votes -
Allow Owners to edit Admin profile information
Owners (i.e. superusers) should be able to administer all the admins/agents registered in the system beyond inviting them, promoting them to owner, or deleting them.
Doesn't have to be extensive, but at least being able to update username, company, or other basic user admin tasks.
3 votes -
Display the total count of ideas, comments, and votes each user has in a list of users
In addition to the karma score, show the number of ideas, comments, and votes spent / remaining per user in the forum>>users listing as well as the associated export.
Mock-up attached.
Now this information is available per user, but that is tedious to review.
Having this info at the aggregate level helps admins to know:
1) how healthy or biased the interaction is (few people writing a lot, or a lot of people writing a little)
2) who are the top contributors in terms of volume
3) how many users have reached their voting limit2 votes -
Be able to export User and Account Traits
User and Account traits give admins valuable data, and it would be even more valuable if it was possible to export those traits as well.
2 votesZenRep has several new export options to help you better analyze messages and users.
- You can now export a list of users almost anywhere in ZenRep – the main users list, users on a message, or in an account. The export includes all the information that we have about the user, including their custom fields, accounts, and location.
-
Provide a “sandbox” site for testing
While setting up and testing SSO (as well as other features), I'm finding that in order to avoid cluttering my live ZenRep with with bogus and mis-matched users, I need to do all of my ZenRep setup and testing in my production app. Would be much better if I could point my development and staging environments to a private ZenRep sandbox that I could play and experiment with (and maybe occasionally wipe clean) instead of having to connect to my live instance.
5 votes -
Export a list of users and their ideas/votes/comments
You can export a list of users. You can export a list of ideas. But you can't export a list of users with their ideas/comments and votes. It would be super helpful if we could see a list of users, and the ideas each user supports.
10 votesZenRep has several new export options to help you better analyze messages and users.
- You can now export a list of users almost anywhere in ZenRep – the main users list, users on a message, or in an account. The export includes all the information that we have about the user, including their custom fields, accounts, and location.
-
Don't allow SSO users to override their email and password
Being on our SSO implementation, we see a major problem with the
ability for users to change their passwords and email addresses while in ZenRep. This gives
the user the impression that they have changed their emails and password in our system as
well, which of course means they can't login to the site.5 votes -
Ability to remove users access to a private Forum when pulling up their profile after a search
You can remove a user's access to a specific private Forum only if you're viewing the list of users for that Forum.
If an Admin searches for a specific user, they don't have the option to control their Forum access from that profile view.
For a small Forum, with a limited number of users, this isn't a huge deal. But if an Admin has over a 50 users on a Forum, this gets tedious (and takes too much time).
Ideally, if an Admin searches for a user, when they open the profile, they should have the option to remove the…
3 votes -
Allow admins to edit user information
Coming from a Community Management background, I am accustomed to having a variety of administrator tools on forums that aren't offered in ZenRep. Among these tools are more robust search features, and a consolidated user information page with the ability to edit user information.
At the present, I cannot search by individual forum and must scroll through multiple pages across four different lists (Voters, Given Access, Invited and Removed) to find users. The results of using the "Search ideas and feedback" feature under Feedback are missing this basic information.
Once a user has been found, I have no way to…
7 votes -
Show votes remaining with user information
When I click on the name of a User, it takes me to a page that shows their ideas and comments. At the top it gives their basic information (e-mail address, member since, last active, etc). In that section it would be nice to see the status of their votes (used and remaining). Thanks!
3 votes -
Merge Users
After implementing SSO we ended up with many duplicate users. This was partially our fault (we didn't define the user id properly when moving over) but even if we had the original pre-SSO user and SSO would still be duplicates.
5 votes -
Allow for a read only users
We have set a limit of 2 users per customer, however, we have customers requesting that a read only user be created. Is there any plans to allow settings against a user to be changed to allow 'read-only' user with no content creation rights?
24 votes
- Don't see your idea?