Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
synapse
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Monitor
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Maunium
synapse
Commits
563606b8
Unverified
Commit
563606b8
authored
6 years ago
by
Richard van der Hoff
Committed by
GitHub
6 years ago
Browse files
Options
Downloads
Patches
Plain Diff
consent_tracking: formatting etc
parent
2574ea3d
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/consent_tracking.md
+7
-8
7 additions, 8 deletions
docs/consent_tracking.md
with
7 additions
and
8 deletions
docs/consent_tracking.md
+
7
−
8
View file @
563606b8
...
...
@@ -31,9 +31,9 @@ Note that the templates must be stored under a name giving the language of the
template - currently this must always be
`en`
(for "English");
internationalisation support is intended for the future.
The template for the policy itself should be versioned
- for example
`1.0.html`
. The version of the policy which the user
has agreed to is stored in
the database.
The template for the policy itself should be versioned
and named according to
the version: for example
`1.0.html`
. The version of the policy which the user
has agreed to is stored in
the database.
Once the templates are in place, make the following changes to
`homeserver.yaml`
:
...
...
@@ -66,7 +66,7 @@ Once the templates are in place, make the following changes to `homeserver.yaml`
3.
Add
`consent`
wherever the
`client`
resource is currently enabled in the
`listeners`
configuration. For example:
```
```
yaml
listeners:
- port: 8008
resources:
...
...
@@ -85,8 +85,7 @@ Once this is complete, and the server has been restarted, try visiting
this should give an error "Missing string query parameter 'u'". It is now
possible to manually construct URIs where users can give their consent.
Constructing the consent URI
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
### Constructing the consent URI
It may be useful to manually construct the "consent URI" for a given user - for
instance, in order to send them an email asking them to consent. To do this,
...
...
@@ -116,7 +115,7 @@ version of the policy. To do so:
*
ensure that the consent resource is configured, as in the previous section
* ensure that server notices are configured, as in [server_notices.md].
*
ensure that server notices are configured, as in
[
server_notices.md
]
(
server_notices.md
)
.
*
Add
`server_notice_content`
under
`user_consent`
in
`homeserver.yaml`
. For
example:
...
...
@@ -141,7 +140,7 @@ notices room is exempted from this).
To enable this, add
`block_events_error`
under
`user_consent`
. For example:
```
```
yaml
user_consent
:
block_events_error
:
>-
You can't send any messages until you consent to the privacy policy at
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment