Recursive permissions?
Support Ticket
+issues
So I've started to go through and set things that users don't need to see to be Administrator or Anyone Logged in. One of these things was Style: common, because users don't need to look at the site's style sheets. I decided they wouldn't need to look at any of them, so I set Admin access on all SCSS. Now in the search results I get SCSS+*type+*read, which is exactly the kind of card I'm trying to eliminate from non-Admin search results. Now if I go and set THAT card to Admin-only read, is it going to make another public card stating that the SCSS+*type+*read+*read itself has a permission?
It will probably become obvious if you try. When you go to edit the rules for that card, you can apply them to just that one card (in which case you could, if you really wanted to, create longer and longer rules, like SCSS+*type+*read+*self+*read), or, more naturally, "all cards ending in *read", or "All "+*" cards".
The simpler way to do this might be to exclude all plus cards from your search results by editing the *search card and adding something like "not":{"right":{}}
Well, I can't make a rule that sets All +* to Read: Admin because then my cards with included queries won't work. Even though I would *like* to do this, because if you search the site for all cards, half the results are nothing a user would want/need/or should see. It's almost literally half, too. I get 38 pages of results, and somewhere around page 20 they stop being content results and start being backend structure results.
It's not that I don't want the plus cards with content being searched. I don't want the blank master plus cards showing up as search results *for users*, because they're blank. And I don't see why users should be getting backend CSS and SCSS pages as possible search results either. But I still need a way to be able to find those things.