Candidate identity review
Review the visible account information that identifies the correct X account before authorization.
X / Connection-only scope
Review the candidate identity of the authorized X account and manage connection, reauthorization and removal without implying publishing access.
PRODUCT VIEW
The X screen lets you connect and manage an account; it does not enable publishing. An authorized user reviews the candidate account returned from the provider’s OAuth step, its visible identity and its relationship to the existing connection, then approves the connection. The account list can show connected, reconnection-required and removed states. This preparation workflow is not intended to publish on X, schedule future posts or read metrics. An account appearing on screen must not be interpreted as evidence that other unfinished X capabilities are available.
FROM NEED TO OUTCOME
A social provider’s logo or account name inside a product can imply that every publishing feature is present. That expectation may lead a team to base its X content plan on a workflow that is not ready.
Assess the X connection according to its actual current scope. Manage the authorized account, consent validity and removal option; do not base publishing or reporting work on an unavailable capability.
STEP BY STEP
Review whether workspace, authorized user, provider configuration and pilot approval are ready for this workflow.
After OAuth, inspect the visible account name or user identity and its relationship to the existing connection to confirm the correct account.
Complete connection approval and, when needed, use reconnection or removal according to the current state.
INSIDE THE MODULE
Review the visible account information that identifies the correct X account before authorization.
Create a connection record for the new or existing identity with user approval.
Treat permission that needs refreshing separately from an active connection.
End the account’s Hubz connection through the existing confirmation step.
Make clear to the team that only connection is provided and publishing, scheduling, analytics and comment capabilities are not enabled.
IN EVERYDAY WORK
The candidate account is approved and its connection status tracked; the team does not begin publishing operations merely because the connection exists.
Scenarios are illustrative; they are not customer testimonials or measured performance claims.
KNOW WHAT IS INCLUDED
This pilot requires separate activation, an authorized administrator, an eligible workspace and the required provider permissions. A social-account allowance alone does not activate it. Availability is confirmed during setup.
YOUR QUESTIONS
The current implementation is connection-only. Publishing and scheduling are not yet enabled.
No. Analytics and comment features are not offered as active capabilities within this connection scope.
RELATED WORKFLOW GUIDES
MODULES THAT WORK TOGETHER
Organize brand rules, content preparation, review, calendars and connected social accounts in a shared workspace.
Set up email, calendar, task-file and approved communication connections with the correct account, permissions and action scope.
Arrange team access through workspace membership, existing roles, enabled modules and connection permissions.