-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DOCS-689 Viridian Organization Documentation #140
DOCS-689 Viridian Organization Documentation #140
Conversation
Updates to navigation, playbooks, and existing, re-used, topics as well as new files for the details
* xref:invite-user.adoc[Invite user] | ||
* xref:remove-user.adoc[Delete user] | ||
* xref:payment-methods.adoc[Manage billing and payments] | ||
* xref:delete-account.adoc[Delete the organization account] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
need to add information on what the user type sees; for example the admin user sees all clusters, org users see only their own clusters. Also, that there is a delay between an update - for example if the org user changes their name - and that change being visible for the admin user
:cloud-order: 60 | ||
:toclevels: 3 | ||
|
||
{description} | ||
|
||
You cannot delete an organization while there are outstanding payments on the account. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You cannot delete an organization while there are outstanding payments on the account. | |
You cannot delete an organization while there are outstanding payments on the account. However, if a payment method is associated with the account, the outstanding payment is processed automatically and the organization is then deleted. |
|
||
== Deleting your Account | ||
. Open the link:{page-cloud-console}[Hazelcast {hazelcast-cloud} console,window=_blank]. | ||
. Select *Account* from the side navigation bar |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe the option to delete the org is moving to the more logical position in the Organization options.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have https://hazelcast.atlassian.net/browse/HZC-6274 to address this
Also added information on the need to reset password before MFA can be enabled if not already set.
@@ -0,0 +1,42 @@ | |||
== Add Payment Method | |||
:description: {hazelcast-cloud} Standard Edition admin users are prompted to add payment details after signing in for the first time. Adding your payment details sets up automatic payments based on your usage. You cannot create clusters until you have added a payment card. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
admin users are prompted to add payment details after signing in for the first time
@rebekah-lawrence admin users are also prompted to add payment details just before they try to create their first cluster. Maybe this is smth we have to mention, not sure though
|
||
NOTE: {hazelcast-cloud} Trial Edition users do not need to add payment details. The payment details for {hazelcast-cloud} Dedicated Edition users are agreed and set up as part of account creation. | ||
|
||
To add your payment details, complete the following steps: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pls see ther comment above regarding the alternative way of adding the payment details
|
||
To create a new account, go to the link:{page-cloud-console}[{hazelcast-cloud} sign-up page, window=_blank]. | ||
NOTE: By creating an account, you are agreeing to the {hazelcast-cloud} link:https://viridian.hazelcast.com/terms-of-service[Terms of Service,window=_blank] and the Hazelcast link:https://hazelcast.com/privacy/[Privacy Policy,window=_blank]. These documents are also vailable from the sign-up page. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo: vailable :)
. Sign into Google if you haven't already. | ||
NOTE: If you use this method, you do not create a {hazelcast-cloud} password. If you subsequently want to sign in with your email and use MFA in {hazelcast-cloud}, you must set a password first. For further information on setting a password, see the xref:change-password.adoc[] topic. | ||
|
||
. Select the *Google* button |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rebekah-lawrence we also have "Github" button for social sign in. JFYI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The GitHub option should be there as a tab, is this not what you are seeing?
[Note that, Karthic's request, the next update will reorder these tabs to Email | GitHub | Google]
|
||
A confirmation email will be sent to your registered email address and you will be signed into the {hazelcast-cloud} console. | ||
A confirmation email is sent to your registered email address and the {hazelcast-cloud} console displays the Cluster screen ready for you to continue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A confirmation email is sent to your registered email
it's not sent in case of social login
@@ -10,6 +10,8 @@ | |||
|
|||
Standard means that Hazelcast manages the cloud infrastructure for you. Each {hazelcast-cloud} Standard cluster is an independent deployment of Hazelcast Platform in a Kubernetes container. This design guarantees resource isolation, prevents resource stealing, and provides isolated network access. | |||
|
|||
When you first create an account on Hazelcast {hazelcast-cloud}, you become the admin user for an organisation. This means that you can invite users to your organization and share resources, such as clusters. For further information on organizations, see the xref:organizations-and-accounts.adoc[Organizations and Accounts] section. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
another place of using organisation and organization in the same sentence :)
@@ -0,0 +1,21 @@ | |||
= Overview | |||
:description: An Organization account allows one or more users to use shared resources, such as clusters. Every account is owned by an organization and is controlled by an admin user. Up to 100 associated organization users can be added. Users can belong to a single organization organization only. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Up to 100 associated organization users can be added
TBH, we don't have this implemented, I've raised https://hazelcast.atlassian.net/browse/HZC-6371 to address this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed org user limit until JIRA implemented
|
||
Admin users can see all clusters. If an organization user is removed, the admin user inherits ownership of the related clusters and resources. | ||
|
||
When updates are made, for example to the state of a cluster or to an organization user's name, there is be a delay between the change being made and the view presented to the admin user. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is be
maybe a typo?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd also state something more optimistic, say, "there might be a delay" :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's because I originally had might be and changed it. Changed back!
docs/modules/ROOT/pages/users.adoc
Outdated
* View and update their profile. For further information on updating your profile, see the xref:view-and-update-profile.adoc[View and Update Profile] topic | ||
* If MFA has not been enforced at organization-level, enable and disable MFA on their account. For further information on enabling and disabling MFA for your sign in, see the xref:user-mfa-settings.adoc[User MFA Settings] topic | ||
* Generate, copy, and delete an API key. For further information on the API key, see the xref:manage-api-key.adoc[Manage API Key] topic | ||
* Change the password used to sign in to their account. For further information on changing the password associated with yuor sign in, see the xref:change-password.adoc[Change Password] topic |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yuor
typo :)
After creating your credentials, ensure that you applications are correctly configured to use the API credentials. | ||
// end::create[] | ||
|
||
IMPORTANT: Keep your keys and secrets secure. Anyone who has these credentials can delete your clusters. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not only delete clusters, but do anything. JFYI
I have brought the docs into line with the current product (MFA enforcement, user limit) and rejigged the payments information to remove the separate Add Payment Method topic and merge the information into the Create Account topic. I've also given it a good read-through, caught some interface changes, ensured any wording changes from the review are applied where applicable, and all that jazz.
|
||
{description} | ||
|
||
NOTE: {hazelcast-cloud} Trial Edition users do not need to add payment details. The payment details for {hazelcast-cloud} Dedicated Edition users are agreed and set up as part of account creation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if we actually have Dedicated Edition users
. Perhaps we don't need this sentence at all The payment details for {hazelcast-cloud} Dedicated Edition users are agreed and set up as part of account creation.
? It adds more questions than answers.
.. Optionally, add the second line of your address in the *Address Line 2 (Optional)* text box | ||
.. Enter your country in the *Country* text box | ||
.. Enter the city used in your address in the *City* text box | ||
.. Enter your post, or zip, code in the *Postal Code* text box |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.. Enter your post, or zip, code in the *Postal Code* text box | |
.. Enter your post, or zip code in the *Postal Code* text box |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's quite strange that we still have this page in docs. We don't support dedicated clusters/users in the way it's described here. I would hide the entire page from the DOCS (and all related pages) and search for all Dedicated related words in the Viridian Cloud documentation to clean that up. But @kthope could confirm on that.
|
||
{description} | ||
|
||
When you generate your API key, you can copy it directly from the Hazelcast {hazelcast-cloud} console. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed "you can" from this sentence - and added a TIP to the Copy section with the extra information.
Updates to navigation, playbooks, and existing, re-used, topics as well as new files for the details