My company is using G-suite and I'd like to analyze basic organization structure details like who's my manager? or who do I manage?
Is this possible using the GoogleApis?
Thanks,
Aubrey
You can definitely consult this information, not by using Gmail API, but by using the G Suite Admin SDK.
Particularly, you may be interested in the following endpoints:
Retrieving a user
Retrieving an organizational unit
You may also want to see the Quickstart which will help you set up an application that can retrieve this data. There are many languages supported (you can choose the one you prefer on the left sidebar).
Related
I have an ASP, vb.net, forms-based system. I want to allow people to use PDF documents created within that system to send them to DocuSign and out to others for signature. I have used the DocuSign SDK to build a system that works; however, I am concerned that I may not have the best setup for that.
The problem relates to the "open" nature of this system. Our users are allowed to see and modify all parts of the underlying system, including forms, coding, etc. As a result, a clientID and secret would be seeable to users. And that is concerning.
The system will need to be set to be easily used by our users. So, having users set up a developer account, setting up API settings, etc., will not be something we can reasonably expect.
It would be better if the system did all the interaction and they just had to log on to DocuSign to send the document out for signing. DocuSign has suggested becoming a partner in their referral system. I worry that will still require all the pieces (clientID and secret) that people will be able to see. But, I am not sure that is true.
Will being a partner mean we can avoid having those items saved in an open system where users can see them? Or does being a partner mean some of that is removed or not necessary?
Is there a better way of setting this up so that we can avoid all that mess?
There's no reason that all your customers wouldn't be able to use the same clientID (also know as Integration Key or IK) and secret key (clientSecret).
You will be the only one that can see/set them as the ISV. They will all use their own DocuSign accounts, using your IK. That is abosltuly fine and does not have any limitations.
We recommend ISVs use a single IK per app if it's the same code for the app even if they have multiple customers using the app.
I would like to be able to supply external users (customers, potential leads, suppliers) across organisations and internal users inside my organisation with documents.
The documents should be organisable per user individually. E.g. Customer A should be able too see documents for the product he bought, not more and not less documents.
No further functionality is currently needed besides that.
Is SharePoint the right tool for that job?
If not what other tools can you recommend from your experience?
I see you tagged SharePoint 2019, I'd advise against using on-prem SharePoint for Sharing documents externally. It is possible, but to do it securely is complex and expensive.
O365 on the other hand is pretty simple and the security is already implemented for you. You can determine the level of access that your external users have and you can extend that by using additional tools provided by Microsoft Information Protection.
You can secure access by forcing guests to login or simply have anonymous links. To add to that you can automate your publishing processes using Power Automate, the O365 workflow.
Take out a trial subscription and make sure it meets all your requirements first.
I have been trying to configure a DocuSign ODBC ( using CData) and came across an issue when trying to get the OAuth credentials.
Based on the Help guide, I see that I need to “Register your DocuSign app”. I am in the API and Keys section on DocuSign but the add app/ integration key button is not there.
Do I need the DocuSign Enterprise plan in order to use this software. This would be an extra cost on our current plan, so I just wanted to make sure first if we need the additional plan to use the ODBC.
https://www.cdata.com/drivers/docusign/odbc/
can you create a developer sandbox (also known as "demo") account? that should have all that you need. You can do that in https://developers.docusign.com
I have some doubts regarding the custom connector we are trying to build for docusign : -
Regarding the license plan that need to be bought by the customers who will be granting access for our connector to collect data from their docusign organization account. I am looking at the link https://www.docusign.com/products-and-pricing. API access support is mentioned in only the advanced solution. So I was wondering whether only we need to have "Advanced solutions plan with APIs support" plan or all our customers need to API access support in order to fetch their data.
As per the documentation, to make the REST API calls we need two fields 'base_uri' and 'account_id' (https://developers.docusign.com/esign-rest-api/guides/authentication/user-info-endpoints). Now, the response of userInfo API call gives an array of accounts and its respective fields. My doubt is, if multiple authenticated users (more than one accounts) are returned in this array but all are part of same organization, will they all have different account_ids. Main concern here is, will there be several Base Paths (https://developers.docusign.com/esign-rest-api/guides/authentication/user-info-endpoints#form-your-base-path) to make API calls?
2a. Further question is, what is the significance of 'is_default' field?
Is this related to main account (if is_default is true) using which we will create our Base Path?
Since this is a tech/engineering forum I'm going to answer only question #2 as question #1 is more of a business/sales question.
The reason you may get multiple accounts is that an authenticated user in DocuSign can be a member of multiple accounts. That said, it's the same user. Meaning, say foobar#blah.com has an account 123 with company X and account 456 with his school, then it's possible that when foobar#blah.com authenticates (With the same password!) to DocuSign we have a list of accounts associated with that user. We give you all of them when you make the API call. The default one is the main one that you would see when you log into our web app. You can decide yourself as the user which one is the default. Users who log into our web-app then see an option at the top-right to change accounts.
and yes, every API call is associated with a specific account. So when you construct the urls for your API - you do need to know which account for this user you are making the API call for. Your application can decide how to handle this.
Hope this helps.
Is there a meteor.js library available for managing user accounts?
I'd like to have users register, have access to unique user IDs to limit the number of times a single user can do something, and also have different tiers of users to control access. It would be great if I didn't have to build this out myself.
Have a look at the accounts api, and the passwords package, which should save you writing most of the boilerplate code for implementing user accounts.
There is also the accounts-ui package with support for facebook, google, and others.
You'll need to implement your own ACL and make sure collections have appropriate permissions.
Finally have a look at the All Tomorrow's Parties demo for some sample implementation.
Shameless plug: Here's an account manager based on the Meteor Roles package -
https://github.com/hharnisc/meteor-accounts-admin-ui-bootstrap-3/
Tutorials included in the readme.