Finish features documentation

docs/development/models.md

@@ -12,7 +12,7 @@ The Django [content types](https://docs.djangoproject.com/en/stable/ref/contrib/
 * [Webhooks](../integrations/webhooks.md) - NetBox is capable of generating outgoing webhooks for these objects
 * [Custom fields](../customization/custom-fields.md) - These models support the addition of user-defined fields
 * [Export templates](../customization/export-templates.md) - Users can create custom export templates for these models
-* [Tagging](../features/tags.md) - The models can be tagged with user-defined tags
+* [Tagging](../models/extras/tag.md) - The models can be tagged with user-defined tags
 * [Journaling](../features/journaling.md) - These models support persistent historical commentary
 * Nesting - These models can be nested recursively to create a hierarchy
 

docs/features/api-integration.md

@@ -1,4 +1,4 @@
-# Integrations
+# API & Integration
 
 NetBox includes a slew of features which enable integration with other tools and resources powering your network.
 

docs/features/authentication-permissions.md

@@ -0,0 +1,49 @@
+# Authentication & Permissions
+
+## Object-Based Permissions
+
+NetBox boasts a very robust permissions system which extends well beyond the model-based permissions of the underlying Django framework. Assigning permissions in NetBox involves several dimensions:
+
+* The type(s) of object to which the permission applies
+* The users and/or groups being granted the permissions
+* The action(s) permitted by the permission (e.g. view, add, change, etc.)
+* Any constraints limiting application of the permission to a particular subset of objects
+
+The implementation of constrains is what enables NetBox administrators to assign per-object permissions: Users can be limited to viewing or interacting with arbitrary subsets of objects based on the objects' attributes. For example, you might restrict a particular user to viewing only those prefixes or IP addresses within a particular VRF. Or you might restrict a group to modifying devices within a particular region.
+
+Permission constraints are declared in JSON format when creating a permission, and operate very similarly to Django ORM queries. For instance, here's a constraint that matches reserved VLANs with a VLAN ID between 100 and 199:
+
+```json
+[
+  {
+    "vid__gte": 100,
+    "vid__lt": 200
+  },
+  {
+    "status": "reserved"
+  }
+]
+```
+
+Check out the [permissions documentation](../administration/permissions.md) for more information about permission constraints.
+
+## LDAP Authentication
+
+NetBox includes a built-in authentication backend for authenticating users against a remote LDAP server. The [installation documentation](../installation/6-ldap.md) provides more detail on this capability.
+
+## Single Sign-On (SSO)
+
+NetBox integrates with the open source [python-social-auth](https://github.com/python-social-auth) library to provide [myriad options](https://python-social-auth.readthedocs.io/en/latest/backends/index.html#supported-backends) for single sign-on (SSO) authentication. These include:
+
+* Cognito
+* GitHub & GitHub Enterprise
+* GitLab
+* Google
+* Hashicorp Vault
+* Keycloak
+* Microsoft Azure AD
+* Microsoft Graph
+* Okta
+* OIDC
+
+...and many others. It's also possible to build your own custom backends as needed using python-social-auth's base OAuth, OpenID, and SAML classes. You can find some examples of configuring SSO in NetBox' [authentication documentation](../administration/authentication/overview.md).

docs/features/customization.md

@@ -2,6 +2,10 @@
 
 While NetBox strives to meet the needs of every network, the needs of users to cater to their own unique environments cannot be ignored. NetBox was built with this in mind, and can be customized in many ways to better suit your particular needs.
 
+## Tags
+
+Most objects in NetBox can be assigned user-created tags to aid with organization and filtering. Tag values are completely arbitrary: They may be used to store data in key-value pairs, or they may be employed simply as labels against which objects can be filtered. Each tag can also be assigned a color for quicker differentiation in the user interface.
+
 ## Custom Fields
 
 While NetBox provides a rather extensive data model out of the box, the need may arise to store certain additional data associated with NetBox objects. For example, you might need to record the invoice ID alongside an installed device, or record an approving authority when creating a new IP prefix. NetBox administrators can create custom fields on built-in objects to meet these needs.
@@ -12,30 +16,57 @@ To learn more about this feature, check out the [custom field documentation](../
 
 ## Custom Links
 
-TODO
+Custom links allow you to conveniently reference external resources related to NetBox objects from within the NetBox UI. For example, you might wish to link each virtual machine modeled in NetBox to its corresponding view in some orchestration application. You can do this by creating a templatized custom link for the virtual machine model, specifying something like the following for the link URL:
+
+```no-highlight
+http://server.local/vms/?name={{ object.name }}
+```
+
+Now, when viewing a virtual machine in NetBox, a user will see a handy button with the chosen title and link (complete with the name of the VM being viewed). Both the text and URL of custom links can be templatized in this manner, and custom links can be grouped together into dropdowns for more efficient display.
 
 To learn more about this feature, check out the [custom link documentation](../customization/custom-links.md).
 
 ## Custom Validation
 
-TODO
+While NetBox employs robust built-in object validation to ensure the integrity of its database, you might wish to enforce additional rules governing the creation and modification of certain objects. For example, perhaps you require that every device defined in NetBox adheres to a particular naming scheme and includes an asset tag. You can configure a custom validation rule in NetBox to enforce these requirements for the device model:
+
+```python
+CUSTOM_VALIDATORS = {
+    "dcim.device": [
+        {
+            "name": {
+                "regex": "[a-z]+\d{3}"
+            },
+            "asset_tag": {
+                "required": True
+            }
+        }
+    ]
+}
+```
 
 To learn more about this feature, check out the [custom validation documentation](../customization/custom-validation.md).
 
 ## Export Templates
 
-TODO
+Most NetBox objects can be exported in bulk in two built-in CSV formats: The current view (what the user currently sees in the objects list), or all available data. NetBox also provides the capability to define your own custom data export formats via export templates. An export template is essentially [Jinja2](https://jinja.palletsprojects.com/) template code associated with a particular object type. From the objects list in the NetBox UI, a user can select any of the created export templates to export the objects according to the template logic.
+
+An export template doesn't have to render CSV data: Its output can be in any character-based format. For example, you might want to render data using tabs as delimiters, or even create DNS address records directly from the IP addresses list. Export templates are a great way to get the data you need in the format you need quickly.
 
 To learn more about this feature, check out the [export template documentation](../customization/export-templates.md).
 
 ## Reports
 
-TODO
+NetBox administrators can install custom Python scripts, known as _reports_, which run within NetBox and can be executed and analyzed within the NetBox UI. Reports are a great way to evaluate NetBox objects against a set of arbitrary rules. For example, you could write a report to check that every router has a loopback interface with an IP address assigned, or that every site has a minimum set of VLANs defined.
+
+When a report runs, its logs messages pertaining to the operations being performed, and will ultimately result in either a pass or fail. Reports can be executed via the UI, REST API, or CLI (as a management command).
 
 To learn more about this feature, check out the [documentation for reports](../customization/reports.md).
 
 ## Custom Scripts
 
-TODO
+Custom scripts are similar to reports, but more powerful. A custom script can prompt the user for input via a form (or API data), and is built to do much more than just reporting. Custom scripts are generally used to automate tasks, such as the population of new objects in NetBox, or exchanging data with external systems.
+
+The complete Python environment is available to a custom script, including all of NetBox's internal mechanisms: There are no artificial restrictions on what a script can do. As such, custom scripting is considered an advanced feature and requires sufficient familiarity with Python and NetBox's data model.
 
 To learn more about this feature, check out the [documentation for custom scripts](../customization/custom-scripts.md).

docs/features/permissions.md

@@ -1,3 +0,0 @@
-# Object-Based Permissions
-
-TODO

docs/features/sso.md

@@ -1,3 +0,0 @@
-# Single Sign-On (SSO)
-
-TODO

docs/integrations/webhooks.md

@@ -85,7 +85,7 @@ A webhook may include a set of conditional logic expressed in JSON used to contr
 }
 ```
 
-For more detail, see the reference documentation for NetBox's [conditional logic](../../reference/conditions.md).
+For more detail, see the reference documentation for NetBox's [conditional logic](../reference/conditions.md).
 
 ## Webhook Processing
 

mkdocs.yml

@@ -61,8 +61,6 @@ nav:
     - Introduction: 'introduction.md'
     - Features:
         - Facilities: 'features/facilities.md'
-        - Tenancy: 'features/tenancy.md'
-        - Contacts: 'features/contacts.md'
         - Devices & Cabling: 'features/devices-cabling.md'
         - Power Tracking: 'features/power-tracking.md'
         - IPAM: 'features/ipam.md'
@@ -70,14 +68,14 @@ nav:
         - L2VPN & Overlay: 'features/l2vpn-overlay.md'
         - Circuits: 'features/circuits.md'
         - Wireless: 'features/wireless.md'
+        - Tenancy: 'features/tenancy.md'
+        - Contacts: 'features/contacts.md'
         - Context Data: 'features/context-data.md'
         - Change Logging: 'features/change-logging.md'
         - Journaling: 'features/journaling.md'
-        - Tags: 'features/tags.md'
-        - Integrations: 'features/integrations.md'
+        - Auth & Permissions: 'features/authentication-permissions.md'
+        - API & Integration: 'features/api-integration.md'
         - Customization: 'features/customization.md'
-        - Object-Based Permissions: 'features/permissions.md'
-        - Single Sign-On (SSO): 'features/sso.md'
     - Installation & Upgrade:
         - Installing NetBox: 'installation/index.md'
         - 1. PostgreSQL: 'installation/1-postgresql.md'