►
From YouTube: Baseline Walkthrough: License Management
Description
Walkthrough of a Secure feature: license management, which is included in our Ultimate tier. It’s important to note that this feature is at a very early stage and is currently considered as an MVP. There are a lot of upcoming improvements so this video will quickly get outdated.
This is part of the GitLab Design team’s Baseline-Experience initiative, where we audit our existing core features quarterly and propose improvement recommendations.
Experience Baseline Documentation: https://about.gitlab.com/handbook/engineering/ux/experience-baseline-recommendations/
Related issues:
https://gitlab.com/gitlab-org/gitlab-design/issues/402
https://gitlab.com/gitlab-org/gitlab-design/issues/478
Secure UX: https://about.gitlab.com/handbook/engineering/ux/stage-group-ux-strategy/secure/
A
Hi
I'm
Kyle
a
product
designer
at
gate,
lab
on
the
secure
team.
Our
design
team
is
currently
doing
an
audit
of
all
of
our
product
stages
and
documenting
our
keys
or
tasks,
also
known
as
jobs
to
be
done
after
we
audit
our
features,
we'll
be
making
recommendations
for
improvement.
We're
calling
this
our
baseline
experience
initiative
and
we'll
be
updating
and
auditing
and
creating
recommendations
quarterly,
as
we
continue
to
iterate
and
improve
our
features
today,
we'll
be
checking
out.
One
of
our
secure
features
license
management,
which
is
a
feature
that's
included
in
their
ultimate
tier.
A
It's
important
to
note
that
this
feature
is
at
a
very
early
stage
and
is
currently
considered
as
an
MVP.
To
put
it
two
more
into
context,
the
primary
user
we
are
designing
for
would
work
in
an
organization's
web
security
department
roles
that
would
benefit
would
have
titles
such
as
security,
analysts,
security
engineers
or
compliance
officers.
Although
for
smaller
organizations
that
might
not
have
a
dedicated
security
department,
this
feature
may
be
handled
by
the
CTO
principal
developer
or
lead
developer
license
management
is
intended
for
compliance
purposes.
A
A
A
One
is
proactive
management
where
the
user
managing
complaints
can
create
and
improve
blacklisted
licenses
prior
to
any
commits
in
a
project
and
then
there's
a
reactive
way
as
well,
which
is
done
when
new
licenses
are
committed
and
the
user
can
decide
at
that
point
to
approve
or
blacklist
an
item.
First,
we'll
take
a
look
at
the
proactive
one
which
would
be
in
our
settings.
A
Okay,
right
now
we're
on
the
project
page
from
here.
The
user
is
looking
for
the
license
management
settings,
they
would
go
to
settings
and
then
CI,
C
D
and
then
the
license
management
section
in
there
it's
hard
to
say,
but
this
may
not
have
been
a
clear
path
for
the
user
they
may,
if
they
were
the
one
that
did
the
configuration
set
up.
They
may
have
remembered
from
the
documentation,
but
if
they
were
unaware
about
this,
this
path
to
this
settings
right
here
may
not
have
been
obvious.
A
Okay,
now
that
we're
here
in
the
license
management,
section
we'll
just
go
ahead
and
expand
that
and
take
a
look
at
what
we
have.
Okay
I
have
a
note
here.
That's
telling
me
that
there
are
currently
no
proved
or
blacklisted
licenses
in
this
project.
All
right,
well,
I'll,
go
ahead
and
add
one
okay,
so
we
added
it
and
I
see
that
there's
a
drop
down
I'll.
Take
a
look
at
that.
Okay,
it
looks
like
there's
a
number
of
already
preset
licenses
in
here.
A
We'll
approve
that
and
now
submit,
and
it
looks
like
that
added
it
to
the
table,
so
this
would
manage
approved
and
blacklist
licenses
for
this
project.
It's
not
clear
to
me
exactly
what
would
happen
next,
though,
as
a
result
of
approving
it,
but
let's
just
take
a
look
at
this
a
little
bit
more
can
blacklist
it
as
well:
okay
and
I'm,
guessing
that
that
would
delete
it.
Okay,
yes,
this
looks
like
it
removes
the
license
from
the
table.
A
What,
if
I,
didn't
see
the
license
on
here
and
let's
say
that
it
was
called,
let's
just
make
up
a
name
called
custom
name
and
pretend
that
was
a
license.
It's
not
clear
to
me
if
I
couldn't
find
the
license.
I
was
looking
for
what
to
do,
but
if
I
just
typed
it
in
here
and
then
hit
enter,
it
does
seem
to
wreck
to
accept
this
custom
entry,
but
that
wouldn't
have
been
obvious
to
the
user
and
I'm
not
really
sure,
if
that
it
can
work.
A
But
let's
test
it
and
let's
say
that
we
want
a
blacklist
this
one,
oh
okay,
it
did
work,
but
it's
unclear
to
me
how
this
would
work,
though,
and
how
the
scanning
detection
would
find
this
license
again.
This
is,
it
was
relatively
easy
to
add
in
licenses
from
the
preset
list
here,
but
I'm
not
really
sure
what
would
be
happening
with
next
steps.
If
I
went
to
all
this
work
to
add
and
to
classify
approved
or
blacklist
licenses,
it's
not
really
clear
to
me
what
what
that
would
do.
A
Okay,
so
now
that
we've
set
things
up
here,
we've
added
a
license:
we've
blacklisted
one,
we've
approved
one.
Let's
take
a
look
at
the
reactive
experience
of
when
new
licenses
are
detected
from
a
commit
and
a
merge
request,
so
I
will
just
go
over
to
this
project.
What
we're
looking
at
now
is
a
merge
request
and
in
the
merge
request
there
are
we
have
the
the
widget
that's
stating
when
the
request
is
made.
It
has
a
pipeline.
A
Let's
take
a
quick
look
at
this
and
want
one
thing
that
is
worth
mentioning
is
the
screen
that
we're
now
looking
at
the
merge
request
and
the
previous
one,
the
settings
one
would
could
be
performed
by
a
maintainer
of
the
project
or
above
so
anyone
who
has
that
level
would
be
able
to
view
this
following
screen.
We'll
take
a
look
at
just
a
participant
below
the
maintainer
level
and
see
what
their
view
would
be
like
in
a
second,
so
I
expand
this
and
I'm.
Assuming
that
the
to
list
items
are
new
licenses
detected.
A
But
it's
unclear
to
me
what
the
categorization
of
them
are.
It
says
LGPL,
so
I'm
guessing
that's
a
license
and
it's
used
by
sidekick.
So
that
could
be
the
package
that
it's
in,
but
again
it's
not
immediately
clear
to
me
and
I'm
a
little
thrown
off
by
the
icons
because
I'm,
assuming
that
the
X
means
that
it's
not
allowed,
but
that
is
there
could
be
a
lot
of
confusion
about
that
and
then
there's
a
sort
of
oval
shape
here
or
circle
shape.
Excuse
me
and
and
I'm
not
really
sure
what
exactly
that
means.
A
A
Okay,
it
looks
like
this
is
the
actual
license
information
for
me
to
read
through
that's
pretty
helpful,
and
it
shows
me
the
packages
that
it's
used
for
so
that's
the
source
of
the
license
and
it
looks
like
I
can
approve
the
license
here,
but
I'm
not
really
sure
what
that
means
is
that,
similar
to
the
approval
button,
we
saw
in
the
merge
request
widget.
Would
it
just
not
sure
it's
it's
not
clear
to
me
what
this
action
would
do,
I'm
guessing
that
it
would
approve
it
for
this
merge
request?
A
Let's
just
take
a
look
at
this
one,
oh
okay,
so
this
is
prompting
me
the
same
way
as
the
other
one
which
is
approved,
license
and
then
down
here.
There's
a
new
call
to
action
that
says
blacklist,
so
I
can
blacklist
or
approve
it.
So
while
in
reality
this
is
actually
creating
a
rule
that
would
work
across
all
projects.
That's
not
really
clear
here
it,
it
seems
like
it
could
be
only
relevant
to
the
merge
request
versus
actually,
if
I
crack
this
license
or
approve
license.
That
would
actually
create
that
rule
across
projects.
A
Okay,
so
now
there's
a
check,
mark
care
and
so
now
I'm
guessing
that
the
X
means
blacklisted.
But
it's
it's
hard
to
tell
all
right
if
I
was
a
user,
that
was
not
a
maintainer
if
I
opened
one
of
those,
what
I
would
see
is
a
similar
modal,
although
it's
just
the
headers
different.
It's
not
prompting
me
with
a
question:
it's
just
showing
the
license
URL
and
packages,
and
it's
not
really
giving
me
a
clear,
call-to-action
or
I'm
not
able
to
do
anything.
So
this
may
be
the
day
to
day
developer.
A
That's
just
committing
new
work,
and
now
these
licenses
were
detected,
but
for
this
user
they're
not
really
it's
not
really
clear
for
what
actions
they
should
take
as
a
result
to
this.
Nor
does
it
give
them
contact
information
of
someone
in
their
organization
that
they
should
approve
this
with,
but
it
does
look
like
the
merge
button
is
active
and
that
they're
able
to
push
this
forward
regardless
of
the
new
licenses
detected,
even
though
one
has
an
X
icon,
which
would
still
be
pretty
unclear
to
the
user.
A
In
terms
of
what
that
means
and
what
they
should
do
as
a
result
of
it
well,
that
concludes
our
audit
of
the
license
management
feature.
As
I
mentioned,
the
feature
is
at
a
very
early
stage
and
there's
a
lot
of
exciting
improvements.
One
thing
we're
working
on
is
making
some
small
changes
around.
This
merge
request
to
clarify
some
of
the
challenges
that
we
walk
through,
as
well
as
actually
disallowing
a
merge
request.
If
a
certain
new
detected
license
has
been
blacklisted
so
certainly
more
to
come
on
that,
and
this
video
will
quickly
get
outdated.
A
In
any
case,
I
really
appreciate
you
checking
out
the
video
we'd
love
to
get
your
thoughts
and
feedback
and
and
any
ideas
about
improvement
and
I
listed.
The
issues
that
we
are
documenting
this
in
into
the
I
linked
them
below
in
the
description
so
feel
free
to
make
a
comment
there
anyway.
Thank
you.