►
From YouTube: Backdrop CMS: Roles and Permissions
Description
This video contains an overview of the roles and permissions system. The intended audience is beginners that have not worked with roles and permissions in Backdrop before.
A
Hello,
my
name
is
tim
erickson.
I
am
st
paul
tim
that
says
tpaul
tim
on
the
internet,
my
company
triplo,
has
a
website
called
simplo,
and
I'm
here
on
behalf
of
simplo
today
to
talk
to
you
about
roles
and
permissions
in
backdrop.
Cms
roles
and
permissions
are
a
basic
building
block
of
something
you
need
to
understand
in
building
your
backdrop
site,
especially
if
you're
going
to
have
more
than
one
person
logging
in
certainly,
if
you
have
any
kind
of
a
membership
site,
this
will
try
to
keep
things
really
basic
in
this
video.
A
This
is
a
beginner
video,
we're
going
to
look
at
two
different
menus
today,
the
user
account
so
roles
and
permissions
are
managed
here.
Under
configuration
user
accounts,
there
are
two
different
user
accounts
or
user
account
menu
items.
In
the
backdrop
admin
menu,
one
of
them
is
all
about
the
roles
and
permissions
and
and
configuration
stuff,
and
one
is
where
you
manage
users.
A
A
A
A
We've
got
to
do
something
about
that
and
under
this
user
account
menu
the
two
things
we're
really
going
to
focus
on
today
I
mean
I'll
just
quickly
say
these
other
things,
like
account,
emails
account
settings.
These
are
various
configuration
options
for
managing
your
users
and
I
think
we'll
handle
that
in
a
different
video.
A
So
for
today's
video
we're
going
to
focus
on
these
last
two
permissions
and
roles,
we're
going
to
look
at
roles
first
and
we're
going
to
see
that
what
backdrop
came
with
out
of
the
box
was
really
four
rolls,
although
one
of
them
is
is
kind
of
the
default
role
of
anybody
visiting
a
site-
that's
not
logged
in.
So
this
is
really
the
absence
of
a
role.
If
you
don't
have
any
other
role,
you're
automatically
anonymous.
A
The
other
three
roles
are
authenticated,
which
that
just
means
that
you
are
logged
in
backdrop
knows
who
you
are,
and
then
we
can
assign
special
permissions
to
anybody.
That's
logged
into
the
site.
We
also
have
an
editor
role,
which
we've
just
created
a
user
with
that
role,
and
we
have
the
administrator
role.
The
administrator
role,
pretty
much
has
permission
out
of
the
box
to
do
everything
that
can
be
changed.
A
There's
two
other
options
here
under
roles:
one
is
what
permit.
What
who
do
you
want
to
get
permission
when
you
enable
new
modules?
So
when
you
enable
a
new
module
on
your
site,
that
has
some
custom
permissions,
who
should
get
permission
to
do
those
things
automatically
by
default?
That's
the
administrator,
but
you
can
change
it
and
you
also
have
the
ability
to
change
what
you
want
to
call
your
anonymous
users
on
your
site.
A
A
Now
we're
going
to
go
back
here
under
user
account
and
go
to
the
permissions
field
or
the
permissions
page.
The
permissions
page
has
a
lot
of
stuff
on
it.
Basically,
our
four
roles
that
we've
already
defined
along
with
a
whole
bunch
of
different
permissions
that
you
can
then
give
to
each
of
those
roles.
A
So
there's
a
lot
of
different
permissions.
You
can
be
very
fine-grained
about
who
can
do
what
in
background
and
you'll
see
that
out
of
the
box.
The
editor,
for
example,
can
access
the
admin
toolbar,
where
a
regular
authenticated
user
can't
let's
scroll
down
here.
So
any
anonymous
user
can
view
comments
as
well
as
any
authenticated
user,
but
only
an
authenticated
user
can
post
comments
or
skip
comment
approval
by
default.
A
So,
let's
just
I
mean
there's
not
much
more,
that's
the
the
basics
of
how
that
works.
What
I
would
like
to
do,
though,
for
you
is
quickly
jump
over
to
another
website
that
we
have
well
it's
the
same
website
just
in
a
different
browser
tab
and
I'm
going
to
log
in
as
that
test
editor
that
we
just
created
a
few
minutes
ago,
just
to
show
you
the
value
of
doing
this.
So
now
I'm
logged
in
as
a
test
user.
A
A
I
do
have
some
handy
links
to
add
new
content.
If
we
go
up
to
the
admin
menu
you
can
see.
This
is
much
simpler,
very
few
things.
The
few
things
that
I
might
want
to
do
things
like
manage
taxonomy
terms,
add
content
and
that's
almost
it
and,
as
you
add,
new
content
types
they'll
show
up
here
in
the
menu,
but
it's
a
much
simpler
menu
for
somebody
that
doesn't
need
all
that
other
stuff
and
it's
going
to
make
their
life
a
lot
easier.
A
Anyways.
There
was
one
more
thing
I
was
going
to
do
with
you
today
and
we'll
go
ahead
and
do
that
now,
which
is
add
a
roll
and
just
show
you
how
that
does
work
under
configuration.
We
can
come
down
to
rolls
and
we
can
add
a
role
and
in
this
case
I'm
going
to
add
a
role
called
brighter.
Maybe
I
want
our
writers
to
be
able
to
create
content,
but
not
to
publish
it.
This
would
be
one
really
good
use
case,
so
I
can
hit
writer
and
there
we
go.
We've
added
that
role.
A
A
We
want
them
to
have
more
access
than
a
regular
user,
but
less
access
than
an
editor
we're
going
to
hit
save
we're
going
to
go
back
to
the
permissions
one
to
just
see
our
change
there.
We
go
now
the
writer's
in
the
middle
there,
but
two
to
go
down
quickly
to
like
the
main
content
area
here.
So
this
is
an
example
of
how
you
would
use
this.
The
editor
pretty
much
has
the
ability
to
so
create
new
content
of
each
type
edit,
their
own
content,
edit.
A
Any
content
delete
their
own
content
or
delete
any
content.
What
you
might
give
the
editor
or
the
a
writer
the
ability
to
do
is
maybe
delete
their
own
content.
Maybe
not
maybe
just
create
their
own
content,
so
we
could
say
that
they
can
create
new
posts
and
they
can
create
new
pages,
but
they
can't
edit
or
delete
them.
Maybe
they
probably
ought
to
be
able
to
edit
their
own,
but
not
other
people's.
There
we
go
anyways,
that's
it
for
our
look
at
roles
and
permissions
for
today.