Jump to content

- - - - -

Basic separation of administrative duties

ACP Restrictions

IP.Content provides the tools needed to create your own site content right from your ACP, and using features built into IPB itself, you can separate these tools so that administrators of your site only have access to the sections they need access to.

For instance, you may have the following basic administrative needs related to IP.Content:

  • Graphic design
  • Web design
  • Editors
All of these duties can be managed via the admin control panel, but you don't need full ACP access to handle any one of these tasks. You can limit graphic designers so that they can only access the Media Manager module of IP.Content from the ACP, for example, so that you don't have to worry about your designer changing some setting they aren't supposed to elsewhere in the ACP. Web designers can be restricted to the Page Templates area only, and editors can be restricted to the Databases and/or Pages modules (depending on how you manage your content).

To limit access to specific modules, you can use the ACP permissions manager from Members tab -> Manage ACP Restrictions. Under "Member ACP Restriction Permissions" click "Find and add administrator". You will be able to lookup the administrator that you wish to restrict, and then configure access to individual areas of the ACP for that specific administrator. Graphic designers who only need to swap out images, for example, can be restricted under the IP.Content tab by checking

  • Grant access to IP.Content application?
  • Grant access to Media Manager module?
Web designers could be restricted to

  • Grant access to IP.Content application?
  • Grant access to Templates module?
  • Grant access to Blocks module?
  • Can create templates?
You could not give the designers access to "Can remove templates?" and prevent that administrator from deleting page templates other admins may still need. Also allowing access to the Blocks module would allow the designers to create the blocks they would likely want to use within their pages.

Editors could be restricted to

  • Grant access to IP.Content application?
  • Grant access to Pages module?
This would allow them to create pages on the site. By using the rich text editor and inheriting the templates created for them by the web designers, the editors can concentrate on the page content itself using a WYSIWYG editor. They do not need to know any HTML at all in this scenario.

Using Databases

An alternative to allowing editors access to the ACP is to use the databases feature of IP.Content 1.1+ to create a simple form that editors can submit from. Instead of giving ACP access to editors, you can create a database, set it to be user-editable, and configure the appropriate permissions. Under the permissions tab you can set which permission masks are allowed to submit content to the database. By leveraging IPB's powerful permission mask system (assigning masks to groups and individual members), you can fine-tune access to submit records to your database.

Using the Databases module, you can create WYSIWYG editor fields, attachment upload fields, calendar date select fields, and most other types of fields you would normally want to create, making it very simple for editors to supply the content you need through a simple standard form interface. Your database can support revisions as well, allowing backups of edited content to be saved before it is updated. Using an attachment upload field, you can allow editors to upload the images they need for their articles, eliminating the need for someone else to upload files they may want to use. You can collect as little or as much information as you need from the editors.

Designers would still need access to Templates in the ACP (and potentially Blocks as described above), but you may have no need to allow graphic designers access to the ACP in this case. They can simply use the attachment field on the front-end form.
  • sobrenome likes this


Developer Docs · Error Codes