SharePoint Reference
SharePoint
This page answers a few questions considering the SharePoint integration of AURUM navigation.
What data is fetched
AURUM Navigation works 100% on the client-side of the user. The app uses the SharePoint REST apis. Those apis are well-known and recommended by Microsoft. Every request is send within the user’s context and respects its granted permissions.
No additional setup is required to enable api usage.
The following apis are consumed:
- Search: Is used to fetch available site collection of the tenant.
- Lists: Is used to fetch available lists within a certain site collection.
- List Fields: Is used to fetch available fields of a certain list or document library.
- List Items: Is used to fetch list items or files of a certain list or document library.
How data is stored
AURUM Navigation doesn’t need any additional lists, services or features to work. All app settings are saved within the WebPart properties of the WebPart instance.
Templates are stored as .json-files within a document library. No additional deployment or installation is needed to use this feature. To learn more on storage location, permissions or scoping check out the templates documentation.
Which permissions are required
No additional permissions are required to use the app.
Learn more about the permissions used by the template feature
Is the full app page feature supported?
Yes. Select AURUM Navigation under page templates.
AURUM Navigation vs SharePoint
AURUM Navigation is a full-featured navigation solution for SharePoint. It provides a wide range of features that are not available in SharePoint out-of-the-box. This document compares the features of AURUM Navigation with SharePoint.
| Feature | AURUM Navigation | SharePoint WP |
|---|---|---|
| Full-page Capability | Yes | No |
| Fully Customizable | Yes | No |
| Advanced Configuration Settings | Yes | No |
| Create/Save/Use Templates | Yes | No |
| Customizable multi-column grid | Yes | No |
| Auto-adjust Mode | Yes | No |