►
Description
UX team reviews and ideates on low-fidelity designs for day I and setup UX for Secure features
A
Pretty
much
I
think
all
of
them,
whether
it's
any
of
Arab
foreskins,
that
we
have
SAS
dependency
scanning
and
containers
and
the
or
license
management
it
requires
that
some
level
of
configuration.
That
is,
that
you
need
to
add
a
file
to
your
project
files
or
a
little
script
to
your
main,
come
fig
file
that
activates,
then
that
triggers
a
pipeline
and
then
the
feature
will
be
active
activated.
If
the
pipeline
succeeds,
because
the
files
were
updated,
we
aren't
doing
a
good
job
at
the
day,
one
for
the
user
I'm.
A
A
It
never
would
have
been
set
up,
so
we're
kind
of
setting
them
down
a
not-so-good
path,
and
so
I
have
a
license
here
where
I'm
sorry
an
issue
here,
it's
not
open,
it's
a
little
too
last-minute,
but
we
have
an
issue
open
around
that
where
we
were
working
with
engineers-
and
it's
really
not
it's
something-
that's
easily
achievable
for
us
to
communicate
that
back
to
the
user,
so
we
can
identify
based
on
the
last
pipeline.
That
was
run
a
small
script
that
says:
did
they
I
add
to
this
script?
A
So
I
took
a
look
at
some
of
the
other
features
yesterday
and
just
show
you
the
day.
One
experience
here
in
the
group
dashboard.
What
we're
looking
at
is
I
got
this
from
our
QA,
because
this
is
actually
coming
down
the
road.
So
just
a
side
note,
this
is
a
little
bit
of
a
new
layout
change
that
we've
been
working
on.
But
anyway,
if
you
landed
here
the
community-
and
this
is
a
group
dashboard-
it's
communicating
to
the
user-
hey.
A
We
found
no
vulnerabilities
for
your
group-
learn
more
about
settings
here,
but
again,
just
like
license
management
that
is
semi,
because
there's
no
setup
here,
we
haven't
even
config
tower
configured
our
files
to
set
up
any
whether
it's
Auto,
DevOps
or
sass
tasks
or
dependency
scanning
container
scanning.
So
once
again
we're
sending
them
down
at
the
wrong
road.
A
So
in
this
case,
if
they
haven't
set
up
any
scanning
or
auto
dev
ops,
we
can
just
let
them
know
and
we
can
leverage
the
documentation
that
we
have
to
say.
Hey
nothing's
been
set
up,
so
let's
not
show
any
UI,
and
here
are
here.
Are
the
reports
that
you
could
have
and
here's
the
links
to
the
documentation
to
set
it
up,
and
in
this
case,
if
you
set
up
auto
dev
ops,
all
the
tests
would
be
configured
now.
A
Let's
say
that
you
just
set
up
one
of
these
tests.
How?
Then
we
can
visualize
this
in
the
dashboard
saying
which
tests
are
setup,
and
this
has
double
importance.
This
is
us
communicating
to
the
user
that
what
files
have
and
haven't
been
set
up,
so
it's
kind
of
giving
them
a
nudge
of
hey.
You
could
set
up
dynamic
testing.
You
could
set
up
dependency
scanning,
just
general
awareness
and
awareness
for
other
users
who
maybe
aren't
the
admin
that
are
coming
to
the
dashboard
and
saying
well,
this
data
that
I
see
in
the
table.
A
A
A
How
are
we
handling
this
elsewhere?
You
know:
are
we
leveraging
that
in
the
UI?
Are
we
leveraging
the
documentation?
Are
we
packing
them?
Are
we
given
them
steps
like
another
step
here?
That
I
could
even
add
is
what,
if
there's
not
a
pipeline
set
up,
so
maybe
we
could.
Just.
These
are
simple
UI
steps
we
could
take
with
what
I'm
getting
feedback
from
engineering
just
simple
scripts
based
on
the
last
pipeline
scan.
So
in
this
case
the
script
would
be.
Has
a
pipeline
even
been
set
up
for
this
project?
A
If
that's
the
case,
then
why
don't
we
link
them
to
the
documentation
to
do
that?
So
that's
kind
of
what
I'm
hacking
on
this
afternoon
I
think
my
first
question
would
be:
have
you
seen
this
elsewhere
anywhere
else
and
get
lab
and
how
they've
handled
these
type
of
situations,
and
maybe
I,
could
leverage
from
that
design
or
kind
of
get
in
line
we
could
align
on
the
designs,
so
I
think
that's
my
first
question.
A
And
if
we
don't
know
that
or
is
there
any,
do
you
think
that
this
helps
the
user?
Is
there
something
that
we
could
be
more
explicit
about
considering
this
experience
of
the
user
just
landing
here,
it
could
be
an
admin,
it
could
be
a
developer.
Are
we
being
clear
about
what's
going
on
here
if
nothing
was
set
up.
B
For
your
first
question,
since
it
sounds
like
the
folks
on
this
call,
don't
know
it
might
be
worthwhile
to
reach
out
in
the
product
channel,
because
the
product
managers
would
be
I,
think
more
likely
to
know,
and
if
that
fails,
you
could
reach
out
in
to
the
general
questions
channel
that
I'd
start
with
the
product
Channel
and
then
I
had
a
quick
question
for
you.
Is
it
that
this
screen
that
you're
on
right
now
and
then
the
other
screen
that
you
were
on
just
before
this?
A
B
B
If
you
set
up
the
Box,
all
tests
will
be
enabled
it's
actually
probably
more
important
than
the
links
above
it
and
so
I
consider
moving
that
up
in
the
content
hierarchy
and
maybe
making
a
little
bit
more
visible,
and
then
we
do
have
a
pattern.
Like
look
I
know
these
are
low
five.
So
if
you're
already
thinking
all
those
facts,
sorry
then
you
know
are
zero
states.
You
know
one
illustration
or
something
for
this
when
you're
ready,
yeah.
C
C
C
A
Yeah
that
that's
great
feedback,
I
agree.
It
could
be
more
peppy
and
aspirational
in
in
the
copy.
So
a
brass
tacks
now
just
to
kind
of
get
the
idea
across
but
I,
especially
like
Auto
DevOps,
because
that
is
that's
what
we
want
to
encourage
right,
because
that's
the
out
of
the
box
experience
I,
think
my
bias
is
probably
because
I
did
this
based
on
some
early
feedback.
We
got
on
some
user
testing
we're
doing
now
and
it's
about
setting
up
sassed
only
so
that's
probably
where
my
my
bias
is
on
that.
B
A
Yeah
and
and
so
I
did
a
quick
flyby
design
review
with
Fabien
like
I
mentioned,
and
my
question
there
was
is:
could
we
eat
like
technically
speaking
kind
of
instead
of
just
sending
them
the
documentation?
Could
we
add
that
script
to
the
config
file?
And
the
answer
is
yes?
Actually,
that's
not
that's
not
that
big
of
a
problem,
and
so
then
the
next
thought
is
is
oh!
A
Well,
if
you
add
it,
then
we
would
maybe
need
an
off
switch,
but
maybe,
as
an
MVC
I
think
the
next
steps
that
I'm
thinking
through
is
that
we
we
could
have
some.
Like
quick,
add
you
add
the
doc,
you
added
the
the
script
to
the
config
file
and
then
maybe
there's
a
some
sort
of
communication
back
to
the
user.
That,
if
you
want
to
remove
this,
you
would
need
to
manually
remove
it
from
the
x
y&z
file
and
that's
only
because
we
you'll
have
some
issues
and
work
to
do
on
getting
our
settings
together.
A
But
anyway,
that's
that's.
Do
you
have
any
thoughts
on
that
of
that
being
an
MVC
if
we
could
get
that
a
bit,
because
that
just
makes
it
so
much
easier?
And
that
gets
us
closer
to
the
out-of-the-box
experience
and
and
again
the
the
insights
that
we're
getting
from
just
setting
up
sassed
alone?
Have
not
the
users
are
really
struggling
on?
What
to
do
where
to
go
so.
B
I
think
it's
a
great
idea
and
I
think
you're
right
for
MVC,
if,
if
you
can
enable
it,
but
you
have
to
you,
know
something
else
to
disable
it,
it's
not
ideal,
but
it's
also
not
terrible.
The
one
thing
I
would
say
back
to
that
previous
screen.
Is
that
something
that's
not
clear
to
me
right
now
with
the
way
the
links
are?
B
Is
that
I'm
going
to
go
to
documentation
and
then
I
think
something
to
consider
is
even
if
you
add
the
capability
to
enable
things
here,
I
still
I
do
want
to
be
able
to
get
to
the
documentation,
though,
because
maybe
I
don't
know
if
I
want
to
enable
it
or
not,
and
then
maybe
we
default
back
to
a
more
standard
pattern
around.
You
know
an
info
icon
or
something
that
indicates
like
hey
we're
like
here's,
where
you
go
for
more
information,
if
you
aren't
ready
to
just
pull
the
trigger.
C
B
A
Yeah,
and
so
so,
there's
a
few
things
to
that
if
they
haven't
set
up
a
pipeline
that
in
that
situation,
that
would
be
a
step
step.
One
set
up
your
conjugal
step.
Two
here
are
reports
that
you
could
then
set
up
and
then
step
three
or
maybe
just
a
note
is
actually
like.
Once
you
set
these
up,
it
will
trigger
a
pipeline
and
then
you'll
be
able
to
see
the
data
on
future
merge
request,
so
it
I
like
the
idea
of
kind
of
showing,
like
incentivizing
them
like
why.
Why
should
I
do
this?
A
B
I
really
like
that,
take
on
it
and
as
a
reminder,
we
do
have
a
marketing
content
team.
So
if
you
want
to
partner
with
someone
just
to
help
you
to
just
really
just
write
the
content
they're
available
and
then,
if
they're,
not
for
whatever
reason,
we
also
have
our
technical
writers,
but
but
I
would
start
with
the
marketing
team
gets
to
Shane's
point.
This
is
this
is
verging
on.
B
A
A
B
A
D
C
D
Well,
so
if
you,
if
you
just
Google
like
empty
states,
you
X,
you
can
find
a
lot
of
inspirational
like
kind
of
just
ideas
but
user
on
board.
Comm
is
one
site
that
just
focuses
on
like
different
ways
of
onboarding
users,
and
they
have
I
was
just
looking
at
it.
Cuz
I
even
looked
at
it
a
long
time,
and
they
have
so
many
use
cases
there's
dozens
of
they
call
them
tear
downs
where
they
go
through
the
onboarding
process
for
a
company
and
web
application
and
talk
about
like
the
different
aspects
of
it.
D
C
Did
link
to
in
the
chat
to
pyjamas
MP
States,
you
could
see
if
any
of
this
is
covered
there
and,
if
not,
maybe
contribute,
because
this
is
hat.
What
you're
solving
for
here
is
an
ad
wide
opportunity
and
one
that
I
I
don't
know
how
well
we
are
not
capitalizing
on,
but
with
a
unified
platform.
That's
definitely
to
our
advantage
to
get
people
to
use
as
many
features
as
possible.
A
It
says
yeah
and
and
I
will
I
have
that
noted
as
well.
It
would
be
nice
to
have
something
go
to
because
it
doesn't
seem
like
there
is
now,
but
there
was
this
one
project
that
I
just
worked
on
this
milestone,
or
we
came
across
this
as
well,
and
we
use
much
more
kind
of
peppy
language
here.
So
this
was
identifying
out
of
date.
Projects
on
your
projects
are
out
of
date
up
to
date,
nice
job,
so
I
think
it
could
be
an
area
where
we
kind
of
a
line
on
and
have
more
fun
there.