[Music]
Hi I'm Caly Moss and I lead the DocuSign
Developer Evangelism Team and
today I'm here with Danny Luoma who's
going to talk about our new Org Admin
feature. So Danny before we dive into the
product if you could talk a little bit
about the teams you've been on at
DocuSign, what your role here is, that would
be great. >> Sure
I'm the lead developer on the administrative
experience here at DocuSign. I currently
work on both internal and external
administration experiences, stuff that
the internal employees need to support
our customers as well as what the
customers need to kind of support their
own accounts and use cases. I've been
here seven years I've worked all over
the product from the API to the sending
experience internal tooling deployments.
You name it, I've kind of done it. >> Awesome.
So what are some of the main advantages
to using org admin? >> Organization admin is
really anybody who has multiple business
units they want to manage. It gives you a
better level of control over the
accounts that are underneath you. You can
create an account for your HR, for your
sales, whatever it happens to be and
manage them from one central location. It
also gives you the ability to claim a
domain and manage at the domain level. >> What does
that mean? >> So domain management would be you can claim
docusign.com, or whatever your domain
happens to be, and then you are in
control of it you can create what
accounts get created using your domain,
it allows you to add users with that
domain, find users that are using that
domain, and already have created free trial
account. It just gives you much
greater control over who has access to
what. >> I see. So I know one of the main
advantages that's unique to org admin is
the ability to auto-activate users. Can
you talk to me a little bit about that
workflow, what that's for? >> Sure. Auto-
activation of users is useful for
customers, because the typical workflow
now without organization admin is: it
will create a new user on the account,
the user gets an activation email, maybe
they don't understand what it means if
you haven't had a company-wide email
telling everybody that they're gonna get
this email, so not really sure if they
should click on it.
What auto-activation ends up doing if
you have a claimed domain is it
automatically creates the user for you
in the system and then when they log in
for the first time they have a user, they
don't have to activate anything it was
already done for them. So you can imagine
a use case, customers are in some sort
of CRM, maybe they have a tie-in directly
to DocuSign when that user comes in to
DocuSign for the first time and clicks
it they automatically have a user,
they're in the system. >> Awesome, so let's
walk through what that auto-activation
workflow would look like for a user
maybe starting in the app so somebody
could see where they would set that up,
where they would take a look at org
admin in the app and then maybe let's look
at some of the calls. >> So from your DocuSign
sending console you go to admin
and if you have organization admin
enabled for your account it drops you in
a different experience than you would
usually see. Normally you would see
the administration experience with your
settings and everything like that. This
is the organization admin UI. From this,
there is a domains tab this is where you
can go in and claim your domain and that
would allow you to auto activate
memberships at that point. So for the API
demo today we're gonna look at Swagger.
In here this is the organization admin
APIs. It lists out all the different
actions you can take underneath these, it
actually shows what you can get to. Today
we're going after users like you
mentioned, the auto activate users, so to
handle this we're going to go - we want
v2 organization. We want to post for
users. >> So and I'm noticing that this is
at the organization's endpoint. Is this
something that's available on our
regular API, or is this something new to
org admin that maybe our devs wouldn't
be familiar with? >> This was just released
on April 18th. >> Okay. >> So this is brand-new
this is the endpoint you're going to be
hitting with whatever your base URL is.
So sandbox environment, it's going to be
on demo, production would be different.
One important thing to note here is the
scopes are called out at each of these
calls. That's Required scopes: user_write.
One of the things that scopes does is
scopes gives greater control over who
has access to what. So a user_write scope
in this case means that you can actually
post users, but if you don't have users_read
you can't read the users. You can't update account
settings as a way to use delegated
permissions. >> And is that going to be part
of the auto-activate flow, that you need
to set a specific scope? >> You're going to
need users_write scope to actually
create a new user in our system.
So here's an example response, but we're
gonna go right past that to the
parameters that we need. So Swagger
actually calls out what is required, I
prefilled some of these already.
That's my organization ID. Here is the
authorization that you need and this
access token will have the scope on it.
>> Okay so what is this access token? Is
this the same access token that you can
get from the developer site that maybe
people would use, you know, for a POC or a
hackathon project when they're working
with the DocuSign API or is this
something specific to org admin? >> This is
handled differently an organization
admin than it's been handled in the past.
We do, through developers.docusign.com
and the resources/tools, give you the
ability to generate one of these tokens,
but this is not the same as what we had
for the eSignature API that required
your integrator key, your username, and
your password. This is handled
differently. So once you have a token you
drop it in here and the nice part about
Swagger here is here's an example
request, so all the parameters you would
possibly need. If you click this it will go
ahead and populate the request for you,
but it has sample strings in there right
now and I've actually edited this
ahead of time. So we're gonna put that
one in. >> So let's take a look here. What
are the most important parts here of
this POST call? I see that we have
accounts, but we also have some user info.
Talk me through what's going on here.
>> From an organization standpoint,
because you can be managing multiple
accounts you're going to want to pick
what accounts you want to create this
new user and permission profile. DocuSign
Sender happens to be a standard
one that we offer out of the box here at
DocuSign, but if you have a custom one
that you would prefer to give this new
user, that's where you would go
ahead and call it out. The bottom stuff
happens to be the user name, the first
name, the last name, the email associated
with new user you want to create, and the default
account ID for them. The one thing to
call out here is this auto-activate
memberships. I have it set to false right
now on my call just for a demo, but if
you turned that to true and you have a
clean domain that's when you get
into the auto-activate scenario. >> Okay,
awesome.
>> So go ahead and click "Try it out!"
>> And what are we waiting for here when we
click that? We're expecting this to do
what? To auto-populate a user, what's
gonna happen here? >> That actually just
made an API call against my environment
that I'm working in and what that
did was created a user in my account. So
here's the curl request for developers
that means here's the response, or
the request URL, that we're actually
pointing against and here's the response
body. So here it created a new person
called Org Sender. There's the email
address for him it was a 200 level
response so we created a new user. >> I see,
and then I can see what account they're
part of? >> Yep this is the account ID they're
part of, the site they have to be in. For
customers and production that realize
that we have multiple data centers this
is important to note. >> I see. Okay great.
And if I wanted to check this out then
to confirm that this user had been
created where would I be able to take a
look at that? >> There's two locations you
can go to look at it. One, as long as
we're in swagger we can do it right from
here and let's do a get users call. Again,
here's the example response you're gonna
get, the required scope for this call and
then down here are the parameters. I
already filled in organization ID, the
account ID I want to look at, and put in
my token. So let's go ahead and try it
out. And here are all the users that
happen to be on my account there's
NewDemo User.
There's Org Demoer we just created. >> Awesome,
thanks for the demo showing everyone how
they can do this both in the UI and with
the API. And Danny if developers wanted
to get started on using org admin where
would they go to take a look at some of
the docs and some of our code examples?
>>developers.docusign.com/orgadmin-api
or in the API drop-down in
the header.
>>Awesome, thanks Danny. >> Thanks Caly. >> Hi,
thank you so much for watching the video if you'd
like to learn the latest and greatest in
DocuSign technology I would highly
encourage you to attend our Momentum
conference and hackathon in June in San
Francisco. It's completely free for
developers.
[Music]