While spaces only have one level of administration (space admin), organizations have two levels: organization admin and organization owner. You may have 1 owner and 9 members 2 owners, 3 admins, 1 developer and 4 members or even 10 owners.Īs for what each of these organization roles can do, it's summarized in the following table: Organization role Let’s say, for example, you have 10 users in your organization. Unlike space roles, organization roles cannot be customized.Īs long as there’s at least one organization owner, you can distribute the roles however you please. There are four fixed organization roles: owner, admin, developer and member. In order to belong to a space, you must belong to the organization containing that space. Organization membership is required for space membership. The following table makes this clear: Space role In order to accomplish any of these three feats, users must be space admins. Space admins alone have the ability to do three things: Overall, we can classify them in two groups: space admin, and everything else. While it's not possible to list all space roles here, as premium plans come with the ability to customize them. Now to get into the nitty gritty about space roles. The previous section distinguished between different sorts of roles and membership: one on the space level and another for organizations. The answer, then: you must be part of the administrative entity before getting to work. Why so? Recall that organizations are for administration and spaces are for working on a particular project. In the case of membership, organization membership is required for space membership. This means that there are two sorts of roles and two sorts of membership: one for spaces and another for organizations. go from medium to large).Īlthough organizations and spaces differ in some clear and important ways, they also share two important things:Īll users that belong to them have roles. You can change your current Contentful plan (e.g. This means of course managing spaces, but also handling monetary matters as well. Generally speaking, organizations are for administration. A common setup we see is for an organization to have some spaces for development (or even for playing around with a few ideas), and others for production projects where editors usually do their work. Moreover, spaces are deleted and created from the organization level. Organizations stand above spaces and contain them. Some familiar settings include:įor instance: you might not want to have the same locales on your homepage as in your PIM system, or you might want to assign specific users the right to create entries of a specific content type. Since different spaces have different goals, each can be configured individually. A space might contain content for a new marketing campaign, for a homepage, for a PIM system, or for anything else. It is not only a collection of content, it’s a collection of content with a certain goal. Practically speaking, however, it is more useful to think of a space as serving a particular purpose. It has its own content model.įrom a simple perspective, spaces house content types, entries, and assets. What are spaces and organizations?Ī space is a workspace that contains all content and media for a project. Together with roles and permissions, they provide the right tools for effective user management. This is why Contentful introduces the distinction between spaces and organizations. For sizable companies, granularity is an important requirement. Fold together: considering both kinds of rolesĪt Contentful, we want to allow our customers to manage their users in a way that truly reflects real-world needs. Let’s see how we can map them into our layout. Our response brings an array of items – those are the videos from our Contentful model. Once we add those two headers, we should start getting a response. The endpoint for the Contentful GraphQL Content Delivery API is: Next, in our example Judo file, we have already added a few things to Judo to get us started – a couple of screens, nav bars, and a Data Source element-which is the layer we use in Judo to connect to API endpoints. Here you can create a new Content Delivery API access token. Open the space that you want to access (the top left corner lists all spaces), and navigate to Settings / Space Settings / API keys. You can create API tokens using the Contentful web app. If you’re setting up your own Contentful integration, you will first need to obtain an API Bearer token.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |