Recently we have purchased a production account. I have logged into the account as Account Administrator but I am unable to see Docusign Admin. This was not the case for the developer account where it was already present from beforehand.
I need it as I have to add an organisation.
Below I have added a picture of how it looks in dev account.
So, most likely you have someone else in your company who is the admin. You will to find out who that is.
Every account has to have one admin at all times. You don't see to have administrative rights, but someone else may have.
If not, or if you don't know who that is - you will need to contact customer support to get this restored and take over as admin.
Another option is that you have multiple accounts in production. Meaning, when you log in, your user is a member of more than one account. You need to switch accounts. That switcher is an option on the right-top menu.
If you had "Admin" in Demo, then someone had to add that as it is not provided by default. Admin tools (Org Management and Access Management w/ SSO) are only included in the Enterprise Pro plan. For Business Pro or Standard plans, it is a paid add-on. Check to see if your account is an Enterprise Pro plan.
Also, if your company already has Org Mgmt, a "DocuSign Admin" (org, not account admin) needs to link this new account to the Org.
Related
I have delegated access to Azure resources in a third-party tenant using Lighthouse, and this works fine via the portal; users receive the roles expected (typically Contributor).
However, they are unable to access Kudu (at webappname.scm.azurewebsites.net), receiving an error;
Selected user account does not exist in tenant 'Tenant Name' and
cannot access the application 'abfa0a7c-a6b6-4736-8310-5855508787cd'
in that tenant. The account needs to be added as an external user in
the tenant first. Please use a different account.
If the same user account is added as a guest to the third-party tenant and given the same role, they can access Kudu as expected.
It's clear that Kudu is expecting/demanding an account in the same tenant as the application, but Azure Lighthouse delegated permissions is all about not having to do that.
Is there something I'm missing, or another role that needs granting?
#PhilD, Thanks for the detailed description of the scenario. I have also posted this on your Q&A thread.
Currently, Kudu is not compatible with Lighthouse-delegated permissions.
Our product engineering team is working on it; however, we do not have an exact ETA to share.
We’re expecting it to be available in a few months. Please note that this timeline is just an estimate and is subject to change, depending on a myriad of factors.
I have relayed the feedback internally to our product engineering team and it’s being tracked.
-On a side note, as mentioned in this Kudu wiki :
“Only those with Contributor / Owner access (to be exact, with microsoft.web/sites/publish/action or, for slot, microsoft.web/sites/slots/publish/action) can access to Kudu (SCM).”
Much appreciate your valuable feedback on this. Thanks for your patience!
Our company has a Microsoft Azure account (Pay-As-You-Go).
We had a programmer that developed our web app. We gave him full access to our Azure account. So, he had access to everything.
We intend to hire another developer to make modifications to the web app, so he'll need access to the App Services and SQL Databases. Our intention is to just allow him access to those features.
We did our research and came across the documentation, Resources, roles, and access control in Application Insights. We followed it step by step, but there's an issue. Doc LINK
We tested the procedure by adding one of our IT staff's Microsoft account (personal Outlook.com account) and assigning him the Contributor role, and sent him an invite. He's not seeing the invite. We did the same for another staff, but it's the same problem.
Can we get some assistance please?
It was not working earlier .I tried with one gmail id. Now it is working perfectly fine and I am able to receive the invitation email.
To send invitation, you need to go to active directory. Add user's email as a guest under add user option (Add guest user).
I initially created a trial account. Discovered that was incorrect then created a developer account. Everything seemed good until I timed out and tried signing back in. The new password used to create the developer account was no longer valid. DocuSign had reverted my account login back to the original trial account. This has happened every time I created a Developer account. I am currently up to my 12th dev account creation. Verifying every time. At least all the fields are prepopulated so I don't have to type everything.
How do I prevent DocuSign account management from reverting my Developer account back to a Trial account? I contacted their support directly but they didn't know and suggested I ask here.
Make sure that you are logging on to demo.docusign.net and that you are going to the following page to set up your dev account. Create Dev Account
When you first login to your account make sure the url is demo.docusign.net. Demo accounts are on a completely separate server system than the production system.
Support should also be able to look up your account information by e-mail to see where your accounts are located and what the status of them are. If you have an enterprise account, I would make sure to have your enterprise account number when you call in. This will put you with the enterprise support group, which typically handles these issues more frequently.
We have a number of Azure subscriptions with various co-administrators in our environment. To date, we have used people's Microsoft accounts to grant co-administrator rights, and of course many use their corporate [username]#[company domain] email address for these.
Some time ago, we enabled Azure directory, synchronized to our on-premise AD, where accounts have also been # - and all was good. When adding new co-admins, we simply had to choose if we wanted to use their MS account or their organizational account.
However, we're now seeing the following error when adding some users' Microsoft accounts to some subscriptions:
The Microsoft Account '[username]#[company domain]' cannot be made a co-administrator as its domain is the same as one of the Verified Domains of the target subscription's directory.
Has anyone else seen this - is it an intentional change in behaviour? It seems somewhat inconsistent...
i had the same issue, then I used the new preview portal and it worked.
try it out
According to Microsoft support, this change in behavior is intentional.
(Since posting the question, they have also sent email notifications that any co-admins with Microsoft accounts outside of the Azure Directory will be added as guest accounts in the subscription's directory.)
Is there a way to create a group admin using the API?
Someone who is able to add and delete users from the group but not from the general administrator account?
I can see there are only 3 permissions profile that can be assigned to a group, Administrator
Thanks.
Currently DocuSign does not use a tiered administrator structure with either the API or their standard console.
Several DocuSign employee's that I've talked with have suggested that a tiered structure is in the works but they don't have a release date for that as yet.
As a temporary fix to this, if you have an account administrator at DocuSign (and depending upon your account set up) you can request that they create sub-accounts to which you can assign groups of users and limit administrators from reaching other accounts. This is the solution we used for multiple business units that didn't need access to each others documents.
You can create more permissions profiles, but the degree to which your users can access settings remains largely the same.
Hope this helps.