►
From YouTube: RBAC Design POD sync: 2022-02-08
Description
Following up on permissions categorization and next steps for the wireframe.
C
So
we
had
kind
of
talked
about
whether
we
should
preserve
that
notion
and
kind
of
have
two
separate
groups
within
our
categorization
scheme,
one
for
projects
and
one
for
groups-
and
we
kind
of
talked
about
when
name
spaces
are
introduced,
that
difference
won't
really
exist
in
the
same
way
anymore
and
so
kind
of
really
collapsing
all
of
those
things
down
into
a
namespace
grouping.
So
I've
gone
ahead
and
done
that
and
I've
pinged
all
of
the
design
pod
members
for
review
and
we've
gotten
a
lot
of
people
a
lot
of
people's
eyes
on
it.
C
C
What
I'm
realizing
is
so
there's
not
only
the
two
permissions
tables
projects
and
groups
there's
also
an
entirely
separate
ci
cd
permissions
table,
in
fact,
there's
a
couple,
different
ones
which
I
just
found
out
about
the
end
of
last
week.
So
there's
been
trying
to
make
sense
of
that
that
there
is
a
whole
separate
list
of
permissions,
and
so
I
think
that's
one
of
the
things
I've
been
working
with,
like
the
technical
writer
and
vitica
to
see.
C
If
there's
a
way,
I
can
include
some
of
those
permissions,
but
I
also
feel
like
I'm
trying
to
be
careful
about
expanding
the
scope
too
much
here,
because
what
we're
trying
to
do
is
capture
the
current
permissions
in
the
table,
but
not
capture.
Everything.
Probably
I'm,
like
I'm
sure,
there's
going
to
be
things
that
we
are
not
going
to
have
in
this
first
batch,
and
I
think
that
that's
probably
okay.
C
But
if
we
add
a
bunch
of
stuff
that
we
actually
don't
want
people
to
control,
which
is
a
little,
what
I'm
worried
about
from
like
the
cicd
tables,
there's
a
lot
of
stuff
in
there.
That
is
very
granular,
and
I
don't
actually
know
if
we
want
all
of
that
stuff
in
the
permissions
table
to
allow
really
that
that
much
tweaking
of
the
permissions
for
cid
cicd.
Maybe
we
do,
but
it
also
seems
like
that's,
really
diving
into
the
deep
end
in
a
way.
B
C
B
Oh
we're,
gonna
start
making
custom
permissions
over
here
in,
say,
icd,
because
we
didn't
have
the
specificity
we
needed
in
the
five
roles
in
the
global
environment,
so
understanding
the
history
of
why
that
exists,
and
is
it
possible
to
break
that
without
breaking
anything
else
or
make
it
merged
into
our
environment?
It
might
just
be
the
case
where
it
has
to
live
in
its
own
thing,
and
that
could
be
you
know
now:
let's
look
at
the
ci
cd
and
do
those
separate,
but
you
know
talking
with
the
back
end
team.
B
C
Yeah,
I
guess
I'm
I'm
not
sure
which
group
he
works
with.
It
sounds
like
from
those
exchanges
with
the
developers
on
that
thread
that
all
of
the
permissions
are
separate
right
now,
so,
like
all
of
them
will
need
to
be
migrated
to
a
different
model,
and
that
was
kind
of
my
takeaway
from
alex
comment.
Was
that
like,
like
that
they're
all
in
separate
files
and
they're
all
going
to
need
to
be
migrated
to
a
single,
maybe
a
single
table?
C
So
it
seems
like
regardless
that
that
there's
gonna
be
some
of
that
migration
that
has
to
occur?
How
much
of
it
we
need
to
do
immediately.
I
feel
like
that's
that
whole,
like
technical
piece
of
this
project
that
I
feel
like
we
I
I
don't
know
at
one
point.
We
start
having
those
conversations,
but
it
feels
like
those
are.
The
that's
gonna
be
the
hard
work
here.
C
B
Should
we
invite
somebody
from
back
end
on
our
next
sink
or
this
sink
to
talk
about
these
things,
because
I
do
I
I
remember
reading
exactly
the
same
thing
you
just
mentioned,
and
it
felt
to
me
like.
Oh,
that
sounds
like
an
opportunity
for
us
to
fix
this
problem
now,
rather
than
having
to
think
about
it
compartmentally
and
having
to
rethink
every
time.
We
have
to
go
back
to
another
permissions
table
and
say
now:
we're
gonna
do
the
pipeline
permissions.
C
B
Think
if
we
back
up
and
say,
let's
reinvest
that
time
and
focus
today
on
making
sure
we
clean
up
the
permissions
across
the
entire
organization
and
then
we
can
proceed
further
down
without
having
to
you
know,
backtrack
or
make
revisions.
But
again,
this
is
all
based
on
how
complicated
that
would
be
yeah.
A
The
guardrails
in
on
this
project
is
probably
the
best
next
step,
even
showing
like
daniel's
wires
and
walking
through,
like
the
general
concepts
and
interactions
that
we're
expecting
or
we
would
want,
and
then
the
data
that
we're
expecting
users
to
interact
with,
which
will
then
lead
into
I'm
sure
down
the
road.
A
more
process-oriented
approach
towards
adding
permissions
from,
like
all
the
other
product
teams.
Can
I'm
sure
you
don't
want
to
be
the
one
that
has
to
go
in
and
change
the
permissions
every
time
that
another
team
makes
an
update.
A
D
A
A
I
mean
if
it
if
it
were
to
ship
as
it
was
today,
it
would
be
a
million
times
better
than
what
we
have,
which
is
nothing,
and
I
think
some
people
may
just
trying
to
fit
in
things
that
may
not
relate,
or
they
hear
permissions
and
think
of
something
different
thinking.
Oh,
we
have
those
here's
this.
It's
not
tracked
in
our
docs,
but
it's
a
thing.
I
mean
every
feature
and
every
click
is
permissioned
in
gitlab,
so
yeah.
C
D
B
A
B
I
think-
and
I
think
also
like
when
we
get
into
chat
with
the
back
end
team,
we'll
have
like
a
lot
of
that
really
fleshed
out
and
finalized
in
terms
of
like
they'll,
say:
oh
yeah,
this
is
exactly
what
we've
been
planning
like
reading.
Andy
alex's
comment
he's
like
this
is
what
the
dream
we've
been
planning
for
a
while.
B
So
it
looks
like
we're,
got
the
support
from
the
back
end
team
already
at
least
from
alex's
perspective,
and
I
think
there
will
be
a
real
interest
in
pushing
that
forward,
because
I
think,
as
as
hannah
had
wrote
here
like
we
don't
have,
we
can't
be
making
changes
permissions
every
time.
Somebody
has
a
new
feature
or
something.
If
there's
a
a
simple
modal
way
of
doing
it
by
saying
new
feature
implement
into
the
system,
spits
out
permissions
and
then
auto
populates
into
the
table
boom
done.
That
would
be
the
dream.
Yeah.
A
C
Well,
I'll
keep
continuing
to
clean
things
up
based
on
everyone's
feedback.
How
how?
How
is
it
most
helpful
for
me
to
kind
of
wrap
this
issue
up
for
for
your
team,
daniel
and
hannah?
I
like,
I
can
post
the
screenshot
in
the
description,
but-
and
I
I
did
some
visual
explorations
and
I
put
those
into
your
figma
file-
are
there
other
things
that
you
feel
like?
B
For
me,
no,
I
think
you
are
done
with
your
portion
and
I
appreciate
the
the
little
wireframes
you've
done
already
and
I'm
going
to
integrate
those
in
the
next
step.
So
that's
what
I'm
going
to
do
next
is
go
back
to
the
flows
and
put
in
these
these
new
tables
kind
of
like
a
higher
fidelity,
mockup
and
prototype.
B
So
we
can
actually
maybe
pass
that
around
up
the
chain
like
the
product,
presentations
and
whatnot,
saying
this
is
what
we're
thinking
about
and
have
it
be
interactive
and
then
also
get
some
validation
with
that
with
end
users.
So
I'm
actually
running
some
tests
right
now
with
some
interviews
with
some
segments
and
I'll
try
and
include
that
in
the
feedback
sessions.
You
know
what
do
you
think
about
this
process,
but
already
like
in
our
interviews
in
the
past,
people
are
asking
for
something
like
what
you've
visualized
already.
So
I
think.
D
B
D
There,
daniel,
I
think,
another
thing
we
could
do
too
or
I
don't
I'm
still
a
little
fuzzy
on
who's
technically
like
where
this
falls,
but
we
do
have
that
list
of
the
dozen
or
so
people
we
interviewed
for
our
research
to
begin
with.
Who
have
said?
Oh,
you
know
once
you
have
a
mock-up
or
something
I'd
be
glad
to
look
at
it,
so
we
can
go
back
to
them
as
well.
B
A
B
B
B
So
I
ask:
how
do
they
set
up
their
permissions?
How
do
they
feel
permissions
limit
or
allow
what
they
want?
Do
they
have
any
restrictions
that
they
are
lacking?
I
kind
of
asked
the
questions
of
kind
of
like
not
posing
a
solution,
but
I
do
say
that
you
know
after
that
I
ask
you
know,
would
you
like
something
more
granular
we're
trying
to
work
on
something
to
improve
the
permissions?
To
add
that
flexibility?
B
A
Okay,
we
want
to
go
through
a
solution,
validation
process.
We
could
try
to
get
those
customers
that
hannah
talked
to,
and
you
know
just
generate
more
confidence
in
the
solution,
not
that
I,
like,
I
don't
think
any
of
us
are
lacking
confidence,
but
I
think
there's,
there's
probably
some
like
good
nuggets
to
pull
out
like
oh
it'd,
be
nice.
If
I
had
this
type
of
information
at
this
part
of
the
flow
so
that
I
could
make
my
decision
easier
or
etc,
etc.
B
I
was
thinking
of
that
exactly
in
the
process
of
making
the
wireframes
is
that
what
more
could
be
added
or
what
more
could
be
taken
out
to
help?
You
know,
make
it
easier
or
make
it
more
understandable
so
like
having
help
or
text,
or
you
know,
info
bubbles
or
any
of
that
sort
of
stuff
necessary.
I
think
that
might
be
where
the
validation
might
come
into.
I
don't
think
the
what
we've
come
up
with
will
have
much
pushback
from
anybody.
A
Yeah
yeah
some
more
stuff
to
fill
out
whatever
could
be
missing
or
help
with
the
roadmap
of
this
particular
feature.
So
then
we'll
be
ending
14
8
next
week,
perhaps
in
149
or
from
now
until
the
end
of
49,
we
can
get
developer
eyes
on
the
prototype
and
their
feedback,
as
well
as
like
some
solution.
Validation
by
the
end
of
49
be
able
to
wrap
this
up
the
mvc.
It
is
and
say
here's
a
validated
solution
from
an
engineering
perspective
and
a
user
perspective
and
here's
our
mvc.
D
D
A
Okay
and
then
I
know
we
had
mentioned
too
as
part
of
this
project
to
have
a
broader
point
of
view,
a
more
extended
vision
of
this.
That
would
probably
be
something
that
we
wouldn't
need
to
deliver
in
14.9.
Is
that
something
that
you
would
like
us
to
still
have
like
something
that
could
be
more
of
a
north
star.
D
A
D
A
B
D
A
B
B
Yeah,
I
think
that's
probably
the
step
I
would
probably
want
y'all's
feedback
on
is
what
should
the
fidelity
of
this
next
prototype
be?
Should
it
be
just
a
walk
through
where
we
say
like
what
the
first
one
was?
I
did
the
video
walkthrough
like
now.
It's
with
higher
fidelity
with
more
you
know,
actual
content,
or
do
you
want
to
make
it
like
really
robust
interactive?
B
My
initial
assumption
would
be
like
just
a
walk
through
with
kind
of
like
the
the
job
to
be
done
like
I
want
to
create
granular
permissions
for
my
team
and
assign
them
to
a
person
or
something
like
that
and
then
walk
through
that
process
again
and
use
that
as
a
presentation,
rather
than
perhaps
an
interactive
prototype
and
then
link
them
to
the
the
issue
for
feedback,
because
then
that
would
prevent
people
from
clicking
around
like.
Why
is
this
not
working?
That's
always
a
problem.
A
They
click
and
they
see
the
blue
boxes
where
they
can
click
yeah.
I
think,
for
the
sake
of
usability
testing
we
want
to
take
them,
give
them
a
few
set
of
tasks
to
achieve
that
are
rounded
enough
to
feel
like.
We
have
confidence
in
and
a
smaller
solution,
and
then
maybe
for
the
socializing
aspect
of
it.
B
So
maybe
like
do
the
first
level
of
the
prototype
with
high
fidelity
and
the
walkthrough
ability,
and
then
the
next
iteration
will
have
the
different
jobs
to
be
done
or
different
tasks
to
go
through
so
adding,
basically
flexibility
or
adding
complexity
to
the
prototype.
I
think
at
that
phase
I'd
probably
ask
for
y'all
to
help
and
can
we,
you
know,
collaboratively
work
on
the
prototype.
You
do
this
flow
and
I'll
do
the
other
flow
or
whatever
yeah.
A
And
now
figma's
had
some
updates
to
their
prototyping
capabilities,
so
it
doesn't.
We
don't
have
to
build
it
out
like
it's
a
1940s
disney
movie
with
every
frame.
I
think
500
frames
to
get
a
click-through
yeah
I'll.
Take
a
look
at
that.
We're
happy,
though
sorry
for
speaking
for
you
amelia,
but
I'm
happy
okay,
great,
so
we're
getting
close
to
time
hannah.
Is
there
anything
we
haven't
discussed
or
any
concerns
that
you
have.
D
C
The
information
architecture
as
we're
validating
the
solution
as
a
possibility,
but
I
didn't
know
if,
if
y'all,
had
thoughts
on
that
or
if
you
feel
like,
we
should
do
a
full,
like
tragic
test
of
to
see
how
everything
stands
separately
from
the
solution.
Validation.
I
just
thought
I
would
ask
that
of
the
group.
Yes,
you've
had
feelings.
B
I
think
your
work
done
already
is
pretty
well
validated,
but
it's
I
guess.
If
you
want
that
external
validation,
I
don't
see
any
problem.
Why
not?
The
only
question
is:
if
you
have
time
to
pursue
it,
I
mean
I
don't
know
where
you
want
to
fit
that
in
your
other
work
or
if
andy
has
an
opportunity
to
help
with
that,
but
I
mean
I
feel
it's
pretty
well
done
already,
so
I
mean
it's
up
to
you.
I
think
how
you
feel
confident
how
confident
you
feel
with
that.
A
A
If
there's
a
lot
of,
if
we
see
a
lot
of
navigation
problems
in
the
usability
test
right
in
this
validation,
the
validation
should
be
broad
enough
to
have
users
going
through
a
few
categories,
not
just
like
one
in
a
checkbox
and
done
so
we'll
be
able
to
get
that
confidence
or
sense
of
confidence
during
the
solution.
Validation,
because
solution,
validation,
isn't
just
the
end
of
the
process,
it
it
couldn't
like
research
can
be
get
researched.
So
that
could
be
our
oh.
The
ia
is
wrong.
A
C
B
D
B
In
the
past,
where
we
only
had
like
one
showcase
and
then
everyone's
like
anybody
want
to
volunteer,
and
so
I
mean
that
was
one
thing
but
yeah,
so
I
don't
know
if,
like
this
would
be
an
opportunity
for
us
to
to
sink
on
that.
I
didn't
know
about
the
emea.
Ux
showcase.
I
didn't
it's
not
on
my
calendar.
I
live
here,
but
I
shipped
my
schedule
to
the
u.s.