See some discussion in D14052. Currently, policy dialogs look roughly like this:

Although this is wordy, it's relatively clear and not easily reducible (it would be nice to say "task" instead of "object", but we'd have to translate like a trillion strings to do that). Generally, for some objects like tasks, the view policy is highly variable and depends on configuration, spaces, etc., and this level of complexity is probably approximately reasonable.

For some other objects like Phortune accounts, we get this dialog:

These are never in spaces, and never have a different object policy. No part of this is actually configurable, and this could be more clear as some static text which is just tailored to explaining how the policies for that object type work.