Add the ability to set specific contacts as private
Sales staff should be able to "protect" their contacts from other sales people from getting deleted, used, shared, etc.
Admins should be able to create a contact then share with particular people of their choice (creating a custom territory for their sales team).
Admin needs more control and 'management' features over team.
ALSO... contacts need to backed up incase they get deleted, in general.... having to update an exported CSV routinely and run the risk of all public contacts among my team will cause me to choose another CRM as we grow.
This is currently in review for our 2017 roadmap.
Any update on this? It's the main reason I cannot bring my company over to Nimble. Otherwise, I love the platform and its UX.
Ben Kim commented
It's now 2017... Any update on this or did this get run over on the 2016 roadmap?
Sean N commented
Been using Nimble for over half a year now and it's got almost everything we need. However, I find myself looking for alternatives simply because we can't use this with our independent sales force. They value the privacy of their contacts and leads.
Will this ever get implement or be stuck in "under review"? 2016 is almost over so I'm not sure how you could possibly add it to your 2016 roadmap.
Please give an update.
We have used Nimble for about 6 months and our team like it very much. However, as CEO I need to be able to administer the system so that some agents can only see their own contacts.
I appreciate that there are many other aspects to security, such as allowing a user to make a contact private. However we would not want such a facility to be made available to our users, and I think our requirements are in line with most sales teams.
So getting back to what we do need, it should be relatively easy to just have one tick box in the admin which applies to each user and says something like "User may only see their own contacts or contacts assigned to them".
Our company is growing and if we don't get this feature soon we will have to stop using Nimble, which is something that we would all hate, but we will have to do it anyway.
I appreciate that apparently this mod has been on your road map for the last two years, targeted for 2016, but can you please supply some feedback as to when it will be made live.
Thanks and regards
Can we have an update on this, or at the very least, let us know how we would recover if an errant person went into the system and deleted records ?
Are there backups made ?
Dang...was almost sold. Then I looked up user permissions and nothing. So I did a google search and came across this thread. Really? Over 2 years, 600+ votes and you are saying first half of 2016??? Wow. Like posted in a few threads before, this is BASIC on a multi user platform. It's like having a $5 Million dollar house...with no doors! For personal use, nothing is better than Nimble IMO. But for teams...I'll come back when you put the doors on.
Christopher Kindig commented
Hello Joseph. Thank you for your response about this.
Could you please update me (and all of us) on the plans for this feature?
I just spent 2 months choosing a system and convincing the entire organization to switch over to Nimble. Then I just checked into this to make sure, and found out to my horror that this one feature does not exist. We absolutely need this common CRM system capability.
Could you please provide a brief update on how it is going, and when you expect it to be ready?
Thank you so much for responding to your fans!
Do we have this now? Has this been adressed?
I have business, political, and personal contacts. I communicate with them all throughout the day. If I'm going to live in Nimble all day (as I used to live in Goldmine), then I need to deal with my contacts and communications all in one place.
Here's how you should implement it. Create completely separate databases for each contact type and manage them independently. Present a unified view of them, though. You can do that very simply by having the search box access all databases that I have access to, and having a unified inbox across email accounts.
Each contact goes in one database, but it can be sync'd with other databases. Contact info like phone and email address are kept up to date across databases. Communications never get sync'd across databases.
Allow me to give permissions to other users at a database level. Nobody gets access to my personal db. People get access to the other dbs as appropriate.
When I leave the company, I can take my personal db with me, but I lose access to the company db. This is really easy if I keep my login forever, and the company just revokes permissions. When I go to the next company, I will have strong incentive to get that company to adopt Nimble.
Sharing communications is a bit trickier. My corporate communications should be open to everyone in the company. By default, my political contacts should be open to political colleagues, but my communications should never be. But sometimes I want to share specific communications. The way to handle this is to allow me to set a default privacy setting for communications for each database, and then have a "share" button on a contact or email.
Don't make the mistake of trying to create virtual databases through some kind of tagging scheme for contacts (the way Highrise does it). Tags get out of control. Have truly separate databases.
2 or 3 hours ago I was pretty convinced that Nimble was the way to do. You have some undeniably great features. But the inability to set private contacts and the inability to convert corporate contacts from Twitter into companies instead of people (as they come in by default) make this product a no go.
Really sorry too. The fact that you have this feature request on your site but have closed the voting without an update telling us when the feature will be implemented just seems like you don't care how people actually use this product.
Canceled to use Nimble due to lack of this feature.
C.J. Jackson commented
This is a must for our company as well... otherwise we cannot do business with Nimble. This was requested 2.5 years ago.... no response... no updates... no progress made on it. This shouldn't be difficult to implement, if you can make messages private you should be able to make contacts private.
We really need this privacy features. We have independent sales people that require this in order to use the system
Guys, come on. Implementing this feature is probably the single most effective thing you can do to get more businesses to sign up. More than voting on G2Crowd, more than sending out direct mails. What's the hang up?
How is this not an option??
What's the status on this?
When will privacy controls for assigning leads to sales teams be available? This almost seems to be a no-brainer feature to implement !
The Business of Hockey Institute commented
P.S. Something else that makes us hesitant to adopt Nimble is the fact that this capability has not been added DESPITE numerous requests for it, as well as the fact that it's been four months since anyone from the company provided an update on this capability. This is so frustrating given how good this product is otherwise.
The Business of Hockey Institute commented
Like so many others, I think Nimble is far away the best unified InBox, communications platform, CRM system available EXCEPT FOR its rudimentary privacy controls. I say that after spending an entire week doing nothing other than evaluating the various options available. Unfortunately, I don't think we can adopt Nimble until it provides our users to control who sees what within their account. As others have noted, with an app that is meant to bring everything together in one place, you'd think this capability would have been built in from the start...
Again, we'd use Nimble if there were access restriction features. As it is, we can't.