►
From YouTube: Compliance: UX Office Hours (2021-10-01)
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
A
We're
aware
a
lot
of
the
changes
we
need
to
make.
It's
just
really
a
matter
of
prioritization.
I
think
the
one
thing
that
I
learned
from
it
is
we
could
do
a
better
job,
including
tech
writing
in
the
messaging
that
we
record
in
our
audit
events
and
that
might
help
alleviate
some
of
the
readability
issues
that
users
might
run
into
when
just
trying
to
read
the
actual
log
itself.
A
Furthermore,
we
have
a
design
pod.
That's
trying
to
address
role-based
access
control
struggles,
so
we're
kind
of
familiar
with
this,
even
from
our
perspective
of
how
we
limit
certain
features
to
the
owner
role.
But
not
every
organization
wants
it.
Just
like
you
know
constrained
to
be
an
owner
or
an
administrator.
Maybe
they
want
to
give
their
auditor
a
specific
role,
or
maybe
they
do
want
to
give
their
developers
a
specific
role,
and
so,
with
that
they're
trying
to
figure
out
how
to
address
that
problem.
A
One
piece
I'm
trying
to
also
vocalize
there
is:
we
do
try
and
track
users,
changes
and
permissions.
So
if
it
gets
more,
granular
like
developers
can
be
given
more
permissions
within
its
own
role.
That
will
probably
need
to
be
added
as
an
audit
event
as
well.
If
it
does
get
to
that
point,
I
also
noticed
there
are
a
few
things
that
were
kind
of
off
about
the
the
mono
space
class
I'll
just
open
up
the
summer.
A
Real
quick
just
to
help
illustrate
so
open
this
up
to
help
make
a
change
we're
currently
putting
like
all
branches
in
monospace,
but
not
actually
the
branch
name,
so
I
think
that's
actually
reversed.
I
was
able
to
fix
it
for
approval
roles.
It
was
a
little
too
fancy
for
me
in
the
view,
file
for
status
check
so
could
quite
figure
it
out.
If
you
want
to
help
me
out,
that's
cool,
if
not
I'll
ping.
Another
engineer
to
help
me.
A
A
Sometimes
it's
actually
a
form
select,
and
so
I'm
going
to
be
better
about
defining
that
either
in
my
designs
are
really
articulating
that
performance,
hopefully
it's
less
annoying
and
it
sets
the
same
expectation
for
what
we'll
see
in
a
change.
And
lastly,
the
date
range
picker
is
getting
some
love,
so
we're
just
kind
of
going
through
some
ideation
on
the
ux
side
to
try
and
bring
in
a
handful
of
improvements
to
it.