Protecting collections or content routes

[mikemartin]

Hey guys,
I'm not sure if this is simply omitted in the Protecting Content doc or a bug. There seems to be no information about protecting collection entries or content routes. Neither of my below examples seem to work.

Collection entries
I would expect to be able to add the protect: logged_in to my collection.yaml, for example:

title: 'Collection'
template: collection/show
layout: layout
protect: logged_in

Content routes
For statamic's content routes I'd also expect to be able to pass my protect config like this:

Route::statamic('/alternate-collection-url/{slug}', 'collection/show', ['protect' => 'logged_in']);

[jackmcdade]

You mean like this? https://statamic.dev/protecting-content

…

On Jul 19, 2020, at 9:23 AM, Mike Martin ***@***.***> wrote:  Hey guys, I'm not sure if this is simply omitted in the Protecting Content doc or a bug. There seems to be no information about protecting collection entries or content routes. Collection entries I would expect to be able to add the protect: logged_in to my collection.yaml, for example: title: 'Collection' template: collection/show layout: layout protect: logged_in Content routes For statamic's content routes I'd also expect to be able to pass my protect config like this: Route::statamic('/alternate-collection-url/{slug}', 'collection/show', ['protect' => 'logged_in'); — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[mikemartin]

@jackmcdade Yes. But I don't see any instructions for Collections or Routes.

[jackmcdade]

@mikemartin I documented the collections bit, but there is currently no way to apply protect to routes. So, we'll call that FR and close this issue since it's not a docs thing.