Changeset View
Changeset View
Standalone View
Standalone View
src/docs/user/userguide/spaces.diviner
Show All 15 Lines | share the same access policy. For example: | ||||
- A contracting company might make spaces for clients, to separate them from | - A contracting company might make spaces for clients, to separate them from | ||||
one another. | one another. | ||||
- A company might create a spaces for consultants, to give them limited | - A company might create a spaces for consultants, to give them limited | ||||
access to only the resources they need to do their work. | access to only the resources they need to do their work. | ||||
- An ambitious manager might create a space to hide her team's work from her | - An ambitious manager might create a space to hide her team's work from her | ||||
enemies at the company, that she might use the element of surprise to later | enemies at the company, that she might use the element of surprise to later | ||||
expand her domain. | expand her domain. | ||||
Phabricator's access control policies are generally powerful enough to handle | Phorge's access control policies are generally powerful enough to handle | ||||
these use cases on their own, but applying the same policy to a large group | these use cases on their own, but applying the same policy to a large group | ||||
of objects requires a lot of effort and is error-prone. | of objects requires a lot of effort and is error-prone. | ||||
Spaces build on top of policies and make it easier and more reliable to | Spaces build on top of policies and make it easier and more reliable to | ||||
configure, review, and manage groups of objects with similar policies. | configure, review, and manage groups of objects with similar policies. | ||||
Creating Spaces | Creating Spaces | ||||
▲ Show 20 Lines • Show All 100 Lines • ▼ Show 20 Lines | |||||
Limitations and Caveats | Limitations and Caveats | ||||
======================= | ======================= | ||||
Some information is shared between spaces, so they do not completely isolate | Some information is shared between spaces, so they do not completely isolate | ||||
users from other activity on the install. This section discusses limitations | users from other activity on the install. This section discusses limitations | ||||
of the isolation model. Most of these limitations are intrinsic to the policy | of the isolation model. Most of these limitations are intrinsic to the policy | ||||
model Phabricator uses. | model Phorge uses. | ||||
**Shared IDs**: Spaces do not have unique object IDs: there is only one `T1`, | **Shared IDs**: Spaces do not have unique object IDs: there is only one `T1`, | ||||
not a separate one in each space. It can be moved between spaces, but `T1` | not a separate one in each space. It can be moved between spaces, but `T1` | ||||
always refers to the same object. In most cases, this makes working with | always refers to the same object. In most cases, this makes working with | ||||
spaces simpler and easier. | spaces simpler and easier. | ||||
However, because IDs are shared, users in any space can look at object IDs to | However, because IDs are shared, users in any space can look at object IDs to | ||||
determine how many objects exist in other spaces, even if they can't see those | determine how many objects exist in other spaces, even if they can't see those | ||||
Show All 18 Lines |
Content licensed under Creative Commons Attribution-ShareAlike 4.0 (CC-BY-SA) unless otherwise noted; code licensed under Apache 2.0 or other open source licenses. · CC BY-SA 4.0 · Apache 2.0