A toolset for professional users of FOI
Everything journalists, researchers and campaigners need to conduct investigations.
Alaveteli Pro’s translations must be translated through Transifex. The Pro-specific translations are presented as an independent resource to translate.
Enabling Alaveteli Pro also enables a new help page that you’ll need to translate in the usual way.
The following are all the configuration settings that you can change in
config/general.yml. When you edit this file, remember it must be in the YAML syntax. It’s not complicated but —
especially if you’re editing a list — be careful to get the indentation
correct. If in doubt, look at the examples already in the file, and don’t use
Alaveteli Pro adds digest notifications for Pro users to help them manage their FOI requests. You must enable the Notifications Daemon when enabling Alaveteli Pro.
There are three possibilities for allowing users to access a Pro account.
|Invite-only||Admins approve or deny access requests.||
|Self-service||Users can add Pro to their account themselves with no intervention.||
|Paid Subscriptions||Users are charged a recurring subscription for access to Pro. See the pricing documentation for more details.||
Assigning your first Pro admin
Alaveteli Pro introduces a new user role of
pro_admin. After enabling
Alaveteli Pro, you’ll need to assign the first
pro_admin through the Rails
$ cd /var/www/www.example.com/alaveteli $ bundle exec rails console
Within the Rails console, find the user you want to upgrade and add the
user = User.find_by(email: 'firstname.lastname@example.org') user.add_role(:pro_admin)
This user will now be able to manage private requests and assign
other users through the admin web interface. Note that
pro_admin users should
also have the
All the Alaveteli Professional settings
Enable Alaveteli Professional.
ENABLE_ALAVETELI_PROis set to true, Alaveteli will include extra functionality and account levels for professional FOI users, e.g. journalists. Professional users have access to a new dashboard, a more streamlined request process, and crucially, the ability to embargo their requests so that they remain private.
Enabling this is a large change, and this is still in Alpha development, so you may want to contact the Alaveteli team before doing so.
Site name for Alaveteli Professional.
The name to use when referring to the Alaveteli Professional parts of an Alaveteli site. For example, in the UK our Alaveteli instance is called "WhatDoTheyKnow" but we refer to the pro parts of the site as "WhatDoTheyKnow Pro".
If you don't want a different name for the pro pages, make this the same as SITE_NAME.
PRO_SITE_NAME: 'Alaveteli Professional'
Contact name and email for Alaveteli Professional.
If you want all support mail to go to the same address, make these the same as CONTACT_NAME & CONTACT_EMAIL.
PRO_CONTACT_NAME: 'Alaveteli Professional Team'
The total number of authorities that can be added to a Alaveteli
Professional batch request.
The email address to which non-bounce responses to emails sent out to
Alaveteli Professional users by Alaveteli should be forwarded.
This option is only used when
ENABLE_PRO_PRICINGis set to
ENABLE_PRO_SELF_SERVEis set to
true, Alaveteli will let users upgrade their accounts to Pro without needing to enter payment details. If
ENABLE_PRO_SELF_SERVEis set to
false, admins will receive an account request email and has to assign the role in the Alaveteli admin interface.