►
From YouTube: Admin for cells/organizations options walkthrough
A
All
right,
Mike,
Nichols
staff
product
designer
for
tenant
scale
here
with
Christina,
looking
through
a
few
options
for
the
admin
area,
since
it
will
now
be
scoped
per
organization
that
does
introduce
a
few
issues
that
we
might
need
to
address.
So
I've
worked
up
a
few
kind
of
early
high
level,
mock-ups
of
what
that
might
look
like,
and
we
will
go
through
those
okay.
So
as
it
is
today,
there
is
the
possibility
where
we
just
kind
of
don't
change
anything.
A
A
So
how
can
an
admin
distinguish
between
those
two
things?
If
we
don't
do
something
to
separate
them,
so
for
like
the
consumption
side
of
things,
I
think
for
things
like
abuse
reports,
it
kind
of
becomes
self-evident,
because
you
can,
you
know
changing
the
organization
will
change
which
ones
you
see
so
that
one,
you
know,
might
not
be
the
worst
thing
in
the
world
I'm
more
concerned
about
like
settings
right.
A
A
The
other
problem
with
that
is
settings.
Settings
probably
needs
to
be
instant
settings
and
organization
settings
and
with
the
pattern
that
we
have
for
settings
there
isn't
really
nested
groups
underneath
settings.
So
this
option
just
doesn't
really
fit
into
our
navigation
pattern
very
well,
although
it
probably
is
like
the
least
amount
of
work
that
we
would
have
to
do
to
solve
this.
So
another
option
would
be
the
reverse
of
that
right.
A
So,
rather
than
trying
to
take
the
instant
things
and
put
them
in
a
section
just
let
it
be
how
it
is
and
introduce
some
sort
of
indication
of
what
organization
that
you're
in
so
basically
giving
it
context
for
the
things
that
need
them.
So
in
this
way
we
could
apply
this
to
settings
and
you
know
also
kind
of
the
aggregation
side
of
things
as
well,
so
this
one
might
work.
A
The
only
downside
to
this
is
their
I
would
say:
there's
predominantly
more
things
that
do
apply
to
the
organization
than
there
are
things
that
apply
it
to
the
instance.
So
we're
going
to
be
adding
in
these
context
or
filters
or,
however,
we
end
up
wanting
to
do
these
to
a
lot
of
places.
So
this
actually
could
be
more
work
to
do
it
this
way
than
it
would
be.
A
A
To
this
option
is
that
you're
kind
of
spreading
settings
that
would
apply
to
an
organization
across
three
things:
the
instance
the
instance
admin
or
sorry
the
instance,
the
org
admin
and
the
org
itself.
Also,
it
seems
like
a
lot
of
work
to
move
all
of
these
things
into
their
own
kind
of
specific
container,
and
if
we're
going
to
do
that,
I
think
there
might
be
another
a
better
way
to
address
that,
so
that
better
way
to
address
that
is
rather
than
move
them
into
kind
of
their
own
world.
A
I
was
thinking
what,
if
we
could
just
move
them
into
the
organization
itself.
This
would
solve
our
long-term
goal
of
bringing
parity
to
from
assassin
self-managed
and
moving
all
this
stuff,
which
we
eventually
do
want
to
move
to
the
organization
anyways.
So
here
we
would
just
have
that
same
kind
of
instance,
admin
setting
and
then
in
the
organization.
We
start
adding
things
in
there.
My
biggest
question
on
this
one
is.
A
A
Don't
even
remember
how
options,
but
obviously
varying
degrees
of
effort,
but
I
think
the
main
problem
we're
trying
to
solve
is
just
how
are
we
going
to
make
it
clear
for
admins
what
is
applicable
to
organizations
and
what
is
applicable
to
the
instance
so
I'll
stop
recording
there
and
I'll.
Add
this
to
the
issue.