►
From YouTube: RBAC wireframes first iteration walkthru
Description
Sr. Product Designer Daniel Mora discusses the first iteration of a flow to create custom roles in an RBAC model in GitLab. See associated epic fo more context. https://gitlab.com/groups/gitlab-org/-/epics/7420
A
So
the
idea
is
here's
a
job
statement.
I
want
to
create
custom
roles
for
my
organization,
so
currently
what
we
do.
We
click
on
the
menu
at
the
top
and
there
would
be
an
admin
section
within
our
self-managed
environment
from
here.
This
is
what
the
the
dashboard
looks
like.
There's
a
few
options
like
users.
A
We
might
need
to
change
headings
because
we
don't
have
a
section
labeled
roles
and
permissions
just
yet
where
we
would
manage
that.
So
perhaps
that's
what
we'll
need
to
look
at
next,
so
this
would
be
a
totally
new
screen.
The
idea
is
that
we
have
our
current
roles
here
in
the
screen
as
an
example,
and
if
you
were
to
select
one,
perhaps
the
permissions
would
show
which
were
populated
or
which
permissions
were
available
for
that
role.
A
This
screen
needs
a
rethink
because
the
idea
of
what
happens
in
an
organization
with
tens
or
hundreds
of
different
types
of
roles.
How
do
you
group
organize
that?
Keep
that
manageable
and
that's
there's
some
other
things
we're
thinking
about
here,
so
the
assumption
being
that
we'll
click
on
a
new
role,
we'll
give
it
a
a
name
and
we
can
select.
A
A
The
idea
here
would
be.
It
would
have
the
base
role
to
copy
permissions
from
so
the
five
roles
we
currently
have
in
gitlab.
We
could
use
this
kind
of
like
a
template,
so
the
idea
that
you
would
select
something
here
would
auto
populate
the
selections
for
you
or
create
kind
of
something
like
a
template
system.
So
you
could
build
from
that
or
revert
if
you
made
a
mistake
and
you
lost
track
of
what
needs
permissions
and
what
doesn't
this
would
also
kind
of
help
with
troubleshooting.
A
So
then
you
would
get
a
success
on
the
creation.
I
think
there
needs
to
be
a-
I
guess:
a
storage
container,
some
way
to
visualize
the
list
of
roles
that
you've
created.
I
don't
know
if
this
is
sufficient
for
that
need,
so
then
they'll
go
so
we'll
want
to
assign
that
enroll
we've
created.
So
let's
go
back
to
menu,
we'll
select
a
group,
so
this
will
be
the
landing
screen
in
the
group.
A
This
is
the
first
item.
Whenever
you
select
group
info
and
then
we'll
go
to
the
members,
I
think
that
those
few
steps
just
there
previously
could
use
some
rethink,
jumping
from
the
creation
to
finding
the
group
and
then
finding
the
section
for
members
and
then
now
finding
the
members
seems
a
little
a
little
cumbersome.
A
A
How
do
we
group
that
or
how
do
we
visualize
that
having
a
list
of
tens
or
hundreds
of
roles
that
seems
not
normal
or
not
usable?
So
there
might
be
a
better
way
to
do
that,
but
just
the
first
iteration
and
then
so
we'll
create
it.
I
invite
that
person
and
then
the
the
user
was
added
to
the
group,
so
that
is
functionally
how
this
first
iteration
these
wireframes
would
work.