Admin sandbox and test account
Would it be possible to have a test account (eg. separate to my admin account, so I can view changes as a user) and an admin sandbox area for developing and testing set-up updates before rollout. NB: I know there is a developer sandbox area, but I'm talking about something an admin can use for testing new set-up changes before applying them.
Best Answer
-
Thanks for providing more details on your context @CPAMD .
I checked with our teams internally, and while sandbox accounts are designed primarily for users to design and test integrations, there are cases where they may be granted for purposes such as what you described. These are approved on a case-by-case scenario, so if you haven't done so yet I recommend signing up to a sandbox account here, and the team will reach out to you.0
Answers
-
Hi @CPAMD , as you mentioned you can contact our team here to request access to a sandbox environment. This environment is aimed at those looking to build apps and integrations for Pipedrive, without having to use a live environment with real data.
What kind of set-up changes do you refer to in this case? If it's trying out new custom fields or pipelines, you can do this on your main account and later modify or remove them without risking all your other data.
0 -
Hi Manuel - Thanks for your reply, but as I mentioned it's not the developer sandbox I'm asking about. What would be helpful is a sandbox environment for admins to change settings etc. before rolling out in a live environment. For example, I've tried changing some visibility groups recently, and my team lost access to their records until I reversed the change.
It's not practical to change settings and then have to revert them if they're wrong, given the impact it has on the team using the CRM. If I had an admin sandbox, with an ability to view the CRM as user (i.e. with reduced permissions) when testing changes, I could avoid that interruption. As it stands, I just avoid making changes, so I know I'm not getting the most out of Pipedrive.
0 -
a good workaround is to create a separate trial account. This lets you test and view changes as a regular user without affecting your main setup.
0