T4029 is the general task for Policy support on Phriction, right now there is no policy support, including anonymous (which we'd be using if we could).

Projects are the privacy setting. You make a Project, set the members and who can join, then lock down other areas of Phabricator with that Project.

I read all this thread and still cannot figure out if I can apply any policy or privacy setting for a project. It is a real trouble. Projects need documentation. But not everyone should access this project.
How does Phabricator approach this issue?

Support Impact Inconsistent and confusing.

Support Impact This is inconsistent, confusing and broken.

This is my number one feature request for Phabricator. A long Wiki page is really hard to edit with the preview at the bottom of the screen. I've often used the Chrome inspector to 'munge' the CSS so I can see the preview on the right, which helps a little.

Thanks

You can replace them with $view_policy = PhabricatorPolicies::getMostOpenPolicy(); safely. That will be "all users" or "public", depending on configuration.

Hmm. Our install is locked down anyways, you can only access it from our network, etc. I don't really care if dropped files are visible to everyone until this is resolved. If I removed these lines, do you foresee any universe destroying consequences?

Not really. If you upload the images by dropping them onto the home page (instead of to the Phriction document) they'll get more open permissions, and then you can manually type {Fnnnn}. Still a lot of work, but maybe a little less bad than fixing the permissions.

Is there a short term solution? Writing documentation with images becomes very tedious if you have to fix the upload permissions on each file, and it's non immediately apparent if you made a mistake and one of the images is viewable only to you.

For us have separate wikis (git accessible even better) would be really great for our use case.

Ideally, we'd fix this by generally modernizing Phriction (beginning with T4029) to pick up this support for free.

T4029 has some discussion about this. The major open question is how powerful to make templating.

✘ Merged into T3963.

◀ Merged tasks: T5804.

If we had an embed syntax (e.g., some syntax like {w/path/to/page}, like {F123} and {P123}) we could apply the same sort of policy rules that we do for the other embed rules -- if you can't see the embedded snippet, you just get a "you can't see this" sort of thing (in the F/P cases we just don't embed it at all and leave the original text, but at some point could maybe show a more explicit "this is a thing that exists which you can't see" output).

bit of a tangent here... re: internal notes, if T5804 sees the light of day, you could store the private stuff wherever, then embed it into the public stuff.