Everything your team needs to deploy, configure, and operate PressGenAI — from first login to daily editorial workflow.
PressGenAI is a white-labelled hyperlocal news platform. When deployed for your newsroom, it runs entirely under your brand and domain — your readers never see PressGenAI. The platform has three user roles:
Stories flow in one direction: contributor submission → AI drafting assistance → editor review → publication on the city page. Nothing reaches readers without editor approval. The editorial chain of responsibility is preserved at every step.
Not a self-service SaaS. PressGenAI deployments are set up by our team — including domain configuration, branding, city page setup, and editor onboarding. You do not need a developer to operate the platform once it is live.
After signing your service agreement, your deployment follows this sequence. Most newsrooms are live and publishing within three weeks.
30-minute call with your PressGenAI contact. We confirm your city list, news categories, branding assets (logo, colours), and custom domain details.
We configure your white-label deployment: domain setup, brand colours, logo integration, city pages, and editorial routing. You receive admin login credentials.
Live training session for your editorial team covering the dashboard, story review workflow, and the approval process. Recorded for future reference.
We provide a contributor onboarding guide customised for your newsroom. You share it with your community through your existing channels.
Platform is live. Contributors are submitting. Editors are reviewing. You are publishing community stories under your brand.
After deployment, you will receive an email with your admin credentials for your PressGenAI publisher dashboard. The dashboard is accessible at community.yournewsroom.com/admin (or your configured subdomain).
On first login you should:
Each city page is an independently managed news feed under your main domain. For example, if your domain is citynews.com, your Maricopa city page lives at citynews.com/maricopa.
City pages can be added, renamed, or archived at any time from your Publisher dashboard. Each city page has:
There is no limit on the number of city pages. Publishers covering a single city typically start with one city page and several neighbourhood sub-categories.
Your platform is configured with the following brand elements during deployment. Prepare these before your kickoff call:
#1A1F5E)community.yournewsroom.com)Brand updates after deployment — logo changes, colour palette updates — can be requested by email and are applied within 2 business days at no additional charge during the active service period.
Categories allow contributors and editors to tag stories by topic. They also drive editorial routing — a "City Government" story can automatically route to your politics editor, while a "Business" story routes to your business desk.
During deployment we configure your initial category set based on your editorial brief. Typical categories include: Local Politics, Business & Economy, Schools & Education, Community Events, Public Safety, Environment, Sports, and Arts & Culture.
Categories can be added or removed from your Publisher dashboard. If a category is removed, existing stories in that category are not deleted — they are uncategorised until reassigned.
Add editors from your Publisher dashboard under Users → Editors → Invite Editor. Each editor needs:
Editors receive an email invitation with login instructions. They do not have access to Publisher-level settings — only the editorial review dashboard.
Editors log in to a centralised dashboard showing all stories routed to them by city and category. Stories appear in four columns:
All editorial decisions (approve, revise, reject) are logged with a timestamp and editor name. The log is visible to Publisher admins.
When an editor opens a pending story they see the full article draft, the contributor's profile, the city and category tags, and the AI-generated confidence score for factual consistency (where applicable).
From the review screen, editors can:
Approved stories publish to the relevant city page immediately or at the scheduled time. Published stories appear with:
Editors can unpublish a story at any time from the dashboard. Unpublished stories are moved back to the Approved column and are not visible to readers.
Community contributors access a separate portal at your platform URL. They register with a name, email, and city affiliation. Registration is open by default; you can require editor approval for new contributors from your Publisher settings.
Once registered, contributors can:
When a contributor begins a new story, they can choose AI drafting assistance. The process:
Contributor picks the city page and news category for their story.
5–8 questions covering who, what, where, when, and why. Contributor fills these in from their own knowledge or reporting.
PressGenAI generates a complete article in your newsroom's editorial voice. Contributor reads and edits before submitting.
Story enters the editor queue. The editorial review process is identical whether AI drafting was used or not.
Editorial voice calibration: During onboarding, we configure the AI with your publication's style guidelines — sentence length, formality, story structure. The output reflects your voice, not a generic AI style. Voice calibration can be updated on request.
Every contributor has a public profile page showing their name, city, a short bio (optional), and a portfolio of their published stories. Profile pages are linked from every published story byline.
Profiles build community journalist identity and create an incentive for contributors to maintain quality — their published bylines are publicly visible.
Publishers can disable public profiles from their dashboard settings if preferred, replacing named bylines with "Community Contributor."
PressGenAI supports multilingual deployments. The platform interface, contributor portal, and AI drafting can be configured for any Unicode-supported language.
Currently in production: English, Marathi, Hindi.
In active configuration: Spanish.
To enable a language for your deployment, email sameer@pressgenai.com with the language and any dialect or regional preferences. Spanish-language deployments can be activated within your standard onboarding timeline.
Your deployment lives on a subdomain or path of your existing domain. You will need access to your domain's DNS settings to add a CNAME record.
community.yournewsroom.com or local.yournewsroom.com); Example DNS record
community.yournewsroom.com. CNAME platform.pressgenai.com.
If you prefer a path-based setup (e.g. yournewsroom.com/community), this is possible with a proxy/reverse-proxy configuration on your existing server. Contact us to discuss.
All active deployments include email support for the duration of the service agreement. First-90-days onboarding support is included in every deployment at no additional charge.
What to include in a support request: Your deployment domain, a description of the issue, any error messages you see, and the email address of the user experiencing the problem. Screenshots help.